| 2 |
Approval of Agenda |
|
| R1-2210800 |
Draft Agenda of RAN1#111 meeting |
RAN1 Chair |
| R1-2210802 |
RAN1#111 Meeting Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2210803 |
RAN1#111 Meeting Management |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2210801 |
Report of RAN1#110bis-e meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2210804 |
LS on SRS in multiple cells |
RAN2, Huawei |
| R1-2210805 |
LS on SL LBT failure indication and consistent SL LBT failure |
RAN2, vivo |
| R1-2210806 |
Reply LS on clarification of RACH prioritisation rules between LTE and NR-U |
RAN2, Ericsson |
| R1-2210807 |
LS on RACH-less handover in NTN |
RAN2, OPPO |
| R1-2210808 |
LS on further questions on feMIMO RRC parameters |
RAN2, Ericsson |
| R1-2210809 |
LS on validity of assistance information |
RAN2, OPPO |
| R1-2210810 |
LS on RAN2 agreements about L1/L2-triggered mobility (LTM) |
RAN2, MediaTek |
| R1-2210811 |
Reply LS on FS_5MBS_Ph2 progress |
RAN2, Huawei |
| R1-2210812 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN2, CATT |
| R1-2210813 |
Reply LS on Terminology Alignment for Ranging/Sidelink Positioning |
RAN2, xiaomi |
| R1-2210814 |
Latency impact for NTN verified UE location |
RAN2, Thales |
| R1-2210815 |
LS on Cell DTX/DRX for NR network energy savings |
RAN3, Huawei |
| R1-2210816 |
Reply LS on FS_5MBS_Ph2 progress |
RAN3, Huawei |
| R1-2210817 |
Reply LS on MTTD for multi-DCI multi-TRP with two Tas |
RAN4, Ericsson |
| R1-2210818 |
LS to RAN1 on NCR-MT transmission and Beam correspondence |
RAN4, CMCC |
| R1-2210819 |
LS on Rel-18 UL Tx switching |
RAN4, China Telecom |
| R1-2210820 |
Reply LS on signalling of CCA configurations of neighbour cells |
RAN4, Nokia |
| R1-2210821 |
LS on RAN dependency for Ranging/Sidelink Positioning |
SA2, xiaomi |
| R1-2210822 |
Response LS on LCS framework for Network verified UE location (NTN) |
SA2, CATT |
| R1-2210823 |
LS on Time Synchronization Status notification towards UE(s) |
SA2, |
| R1-2210824 |
LS Out on Positioning Reference Units |
SA2, CATT |
| R1-2210825 |
LS on LPHAP information delivery to RAN |
SA2, Huawei |
| R1-2210826 |
LS on XR and Media Services |
SA2, vivo |
| R1-2210957 |
Draft reply LS to RAN1 on NCR-MT transmission and Beam correspondence |
vivo |
| R1-2210958 |
Draft reply LS on LPHAP information delivery to RAN |
vivo |
| R1-2210959 |
Draft reply LS on positioning reference unit |
vivo |
| R1-2210960 |
Draft reply LS on RAN dependency for Ranging/Sidelink Positioning |
vivo |
| R1-2210961 |
Draft reply LS on SRS on multiple cells |
vivo |
| R1-2210962 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
vivo |
| R1-2210963 |
Draft reply LS on validity of assistance information |
vivo |
| R1-2210964 |
Draft reply LS on RACH-less HO |
vivo |
| R1-2210965 |
Draft reply LS on feMIMO RRC |
vivo |
| R1-2211054 |
Discussion of LS on XR and Media Services |
Ericsson Inc. |
| R1-2211090 |
Draft reply LS to RAN2 on further questions on feMIMO RRC parameters |
ZTE |
| R1-2211101 |
[Draft] Reply LS to RAN2 on validity of assistance information |
ZTE |
| R1-2211102 |
Discussion on the LS on validity of assistance information |
ZTE |
| R1-2211103 |
[Draft] Reply LS to RAN2 on RACH-less handover in NTN |
ZTE |
| R1-2211104 |
Discussion on the LS on RACH-less handover in NTN |
ZTE |
| R1-2211105 |
[Draft] Reply LS to RAN4 on NCR-MT transmission and Beam correspondence |
ZTE |
| R1-2211106 |
Discussion on the LS on NCR-MT transmission and Beam correspondence |
ZTE |
| R1-2211135 |
Discussion on RAN dependency for Ranging/Sidelink Positioning |
CATT |
| R1-2211136 |
Draft reply LS on RAN dependency for Ranging/Sidelink Positioning |
CATT |
| R1-2211137 |
Discussion on Positioning Reference Units |
CATT |
| R1-2211138 |
Draft reply LS on Positioning Reference Units |
CATT |
| R1-2211139 |
Discussion on LPHAP information delivery to RAN |
CATT |
| R1-2211140 |
Draft reply LS on LPHAP information delivery to RAN |
CATT |
| R1-2211141 |
Draft reply LS on NCR-MT transmission and Beam correspondence |
CATT |
| R1-2211164 |
Discussion of SA2 reply LS on XR and Media Services |
CATT |
| R1-2211165 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
CATT, GOHIGH |
| R1-2211216 |
Draft reply LS on further questions on feMIMO RRC parameters |
CATT |
| R1-2211261 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
LG Electronics |
| R1-2211299 |
Draft reply LS on active TCI state list for UL TCI |
Lenovo |
| R1-2211332 |
[Draft] Reply LS on Positioning Reference Units |
xiaomi |
| R1-2211333 |
[Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure |
xiaomi |
| R1-2211378 |
Draft Reply LS on RAN dependency for Ranging/Sidelink Positioning |
Intel Corporation |
| R1-2211432 |
Discussion on LS on further further questions on feMIMO RRC parameters |
OPPO |
| R1-2211438 |
Discussion on LS Out on Positioning Reference Units |
OPPO |
| R1-2211439 |
Discussion on LS Out on SRS in multiple cells |
OPPO |
| R1-2211448 |
Discussion on the LS on RAN dependency for Ranging/Sidelink Positioning |
OPPO |
| R1-2211449 |
Discussion on the LS on SL LBT failure indication and consistent SL LBT failure |
OPPO |
| R1-2211464 |
Discussion on reply LS on validity of assistance information |
OPPO |
| R1-2211465 |
Draft reply LS on validity of assistance information |
OPPO |
| R1-2211466 |
Discussion on RACH-less handover in NTN |
OPPO |
| R1-2211467 |
Draft LS reply on RACH-less handover in NTN |
OPPO |
| R1-2211494 |
Draft Reply LS on SRS in multiple cells |
ZTE |
| R1-2211495 |
Draft Reply LS on RAN dependency for Ranging and Sidelink Positioning |
ZTE |
| R1-2211496 |
Draft Reply LS on Positioning Reference Units |
ZTE |
| R1-2211497 |
Draft Reply LS on LPHAP information delivery |
ZTE |
| R1-2211542 |
Draft reply LS on further questions on feMIMO RRC parameters |
Spreadtrum Communications |
| R1-2211543 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
Spreadtrum Communications |
| R1-2211544 |
Reply LS on RAN dependency for Ranging/Sidelink Positioning |
Spreadtrum Communications |
| R1-2211550 |
Draft reply LS on XR and Media Services |
vivo |
| R1-2211583 |
Discussion on the LS on SL LBT failure indication and consistent SL LBT failure |
Lenovo |
| R1-2211655 |
Discussion on SRS in multiple cells |
CMCC |
| R1-2211784 |
Draft LS response on feMIMO RRC parameters |
Apple |
| R1-2211785 |
Discussion on RAN2 LS on RACH-less Handover in NTN |
Apple |
| R1-2211786 |
Draft Reply LS to RAN2 on RACH-less Handover in NTN |
Apple |
| R1-2211787 |
Discussion on RAN2 LS on Validity of Assistance Information |
Apple |
| R1-2211788 |
Draft Reply LS to RNA2 on Validity of Assistance Information |
Apple |
| R1-2211789 |
Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT |
Apple |
| R1-2211790 |
Draft Reply LS to RAN2 on SL LBT failure indication and consistent SL LBT |
Apple |
| R1-2211858 |
Draft Reply LS on Positioning Reference Units |
Intel Corporation |
| R1-2211898 |
Discussion on XR and Media Services |
ZTE, Sanechips |
| R1-2212014 |
Draft reply LS on NCR-MT transmission and Beam correspondence |
Samsung |
| R1-2212015 |
Draft reply LS on further questions on feMIMO RRC parameters |
Samsung |
| R1-2212016 |
Draft reply LS on Positioning Reference Units |
Samsung |
| R1-2212077 |
Draft Reply to SA2 LS on RAN dependency for Ranging/Sidelink Positioning |
Qualcomm Incorporated |
| R1-2212078 |
Draft Reply LS on RACH-less HO |
Qualcomm Incorporated |
| R1-2212079 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
Qualcomm Incorporated |
| R1-2212164 |
Draft Reply LS on further questions on feMIMO RRC parameters |
Nokia, Nokia Shanghai Bell |
| R1-2212191 |
DRAFT Reply LS on further questions on feMIMO RRC parameters |
Ericsson |
| R1-2212199 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
ZTE, Sanechips |
| R1-2212210 |
Draft Reply of LS on further questions on feMIMO RRC parameters |
Google |
| R1-2212215 |
[Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure |
Ericsson |
| R1-2212216 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
Ericsson |
| R1-2212278 |
Discussion on Reply LS on RAN dependency for Ranging/Sidelink Positioning |
Xiaomi Technology |
| R1-2212342 |
Draft Reply LS on NCR-MT transmission and beam correspondence |
Ericsson |
| R1-2212343 |
Discussion on RAN4 LS on NCR-MT transmission and beam correspondence |
Ericsson |
| R1-2212448 |
Discussion of RAN2 LS on SL LBT failure indication and consistent SL LBT failure |
Nokia, Nokia Shanghai Bell |
| R1-2212449 |
[Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure |
Nokia, Nokia Shanghai Bell |
| R1-2212462 |
Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT failure |
Huawei, HiSilicon |
| R1-2212467 |
Discussion on LS on XR and Media Services based on SA2 outcomes |
Huawei, HiSilicon |
| R1-2212473 |
Discussion on SRS in multiple cells |
Huawei, HiSilicon |
| R1-2212474 |
Draft reply LS on SRS in multiple cells |
Huawei |
| R1-2212475 |
Discussion on positioning reference unit |
Huawei, HiSilicon |
| R1-2212476 |
Discussion on LPHAP information delivery to RAN |
Huawei, HiSilicon |
| R1-2212477 |
Draft reply LS on LPHAP information delivery to RAN |
Huawei |
| R1-2212478 |
Discussion on RAN dependency for Ranging/SL positioning |
Huawei, HiSilicon |
| R1-2212486 |
Draft reply to LS on RACH-less handover in NTN |
Huawei, HiSilicon |
| R1-2212487 |
Draft reply to LS on validity of assistance information |
Huawei, HiSilicon |
| R1-2212488 |
Discussion on LS to RAN1 on NCR-MT transmission and Beam correspondence |
Huawei, HiSilicon |
| R1-2212489 |
Discussion on further questions on feMIMO RRC parameters |
Huawei, HiSilicon |
| R1-2212498 |
draft reply LS on SRS in multiple cells |
Ericsson |
| R1-2212499 |
draft reply LS on Positioning Reference Units |
Ericsson |
| R1-2212500 |
draft Reply LS on LPHAP information delivery to RAN |
Ericsson |
| R1-2212988 |
LS to capture Text Proposal for TR 38.859 |
RAN2, CATT |
| R1-2213019 |
LS on RAN2 TP for Network energy savings for NR |
RAN2, Huawei |
| 7.1 |
Maintenance on NR Releases 15 |
|
| R1-2210956 |
Clarification of CSI reporting (Rel-15) |
Ericsson |
| R1-2211280 |
On SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2211281 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2211522 |
Correction on slot counting for PUCCH repetition in Rel-15 |
CATT |
| R1-2211523 |
Correction on slot counting for PUCCH repetition in Rel-16 |
CATT |
| R1-2211524 |
Correction on slot counting for PUCCH repetition in Rel-17 |
CATT |
| R1-2211577 |
Draft 38.212 CR on CSI reporting |
Ericsson |
| R1-2211578 |
Draft 38.214 CR on CSI reporting |
Ericsson |
| R1-2211791 |
CSI reference resource for aperiodic CSI report with periodic or semi-persistent measurement resource |
Apple |
| R1-2212017 |
Discussion on clarification of subband CSI reporting |
Samsung |
| R1-2212080 |
Draft CR Clarification on timelines for power control command |
Qualcomm Incorporated |
| R1-2212161 |
Handling of TPC command accumulation for power limited case |
Ericsson |
| R1-2212480 |
Corrections to the timelines for applying group power control command |
Huawei, HiSilicon |
| R1-2212484 |
Discussion on UE FG3-1 for Rel-15 UEs |
Huawei, HiSilicon |
| R1-2212496 |
Discussion on CSI reporting |
Huawei, HiSilicon |
| R1-2212578 |
Summary of CSI reference resource for aperiodic CSI report with periodic or semi-persistent measurement resource |
Moderator (Apple Inc.) |
| R1-2212660 |
Power control command timelines |
Moderator (Qualcomm Incorporated) |
| R1-2212736 |
Summary of slot counting for PUCCH repetition |
Moderator (CATT) |
| R1-2212792 |
Discussion on clarification of CSI reporting |
Moderator (Ericsson) |
| R1-2212798 |
Clarification on timelines for power control command |
Moderator (Qualcomm Incorporated) |
| R1-2212799 |
Power control command timelines |
Moderator (Qualcomm Incorporated) |
| R1-2212811 |
[111-R15-NR] Moderator summary on SCell Type 1 virtual PHR reporting |
Moderator (Nokia) |
| R1-2212861 |
Summary of Rel15 Maintenance on TPC command accumulation for power limited case |
Moderator (Ericsson) |
| R1-2212889 |
Clarification on timelines for power control command |
Moderator (Qualcomm Incorporated), Samsung |
| R1-2212890 |
Clarification on timelines for power control command |
Moderator (Qualcomm Incorporated), Samsung |
| R1-2212968 |
Draft 38.212 CR on CSI reporting |
Ericsson, Samsung, Qualcomm |
| R1-2212969 |
Draft 38.214 CR on CSI reporting |
Ericsson, Samsung, Qualcomm |
| R1-2212995 |
CR on CSI reporting |
Ericsson, Samsung |
| R1-2212996 |
CR on CSI reporting |
Ericsson, Samsung |
| 7.2 |
Maintenance on NR Releases 16 |
|
| R1-2210860 |
Correction on Priority rules for CSI reports in TS 38.214 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2210919 |
Discussion on cases for prioritization related to PUSCH in TS 38.213 and TS 38.214 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2210920 |
Correction on UL prioritization cases related to SP-CSI in TS 38.213 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2211282 |
On UE type “SwitchedUL” and simultaneous transmission on two UL bands |
Nokia, Nokia Shanghai Bell |
| R1-2211283 |
Rel-16 Correction to UE type “SwitchedUL” and simultaneous transmission on two UL carriers |
Nokia, Nokia Shanghai Bell |
| R1-2211284 |
Rel-17 Correction to UE type “SwitchedUL” and simultaneous transmission on two UL bands |
Nokia, Nokia Shanghai Bell |
| R1-2211520 |
Correction on reference clauses for UCI multiplexing and PUCCH transmission in Rel-16 |
CATT |
| R1-2211521 |
Correction on reference clauses for UCI multiplexing and PUCCH transmission in Rel-17 |
CATT |
| R1-2211633 |
Draft TP for UL Tx switching for non-simultaneous transmission on two UL bands |
ZTE |
| R1-2211634 |
Discussion on timeline for UL Tx switching triggered by PUCCH with HARQ-ACK |
ZTE |
| R1-2211792 |
On Rel-16 UL Tx switching for PUCCH with HARQ-ACK |
Apple |
| R1-2212308 |
Correction on capability parameter name alignment for multiplexing HARQ-ACK without PUCCH on PUSCH |
Sharp |
| R1-2212490 |
Corrections on scheduling restrictions between serving cells for UL Tx switching |
Huawei, HiSilicon |
| R1-2212491 |
Corrections on scheduling restrictions between intra-band serving cells for UL Tx switching |
Huawei, HiSilicon |
| R1-2212501 |
Maintenance for NR positioning support |
Ericsson |
| R1-2212617 |
Summary #1 on priority rules for CSI reports |
Moderator (Huawei) |
| R1-2212687 |
UL Tx switching for PUCCH with HARQ-ACK (continuation of [110bis-e-NR-R16-10]) |
Moderator (Apple) |
| R1-2212737 |
Summary of reference clauses for UCI multiplexing and PUCCH TX |
Moderator (CATT) |
| R1-2212773 |
Summary #2 on priority rules for CSI reports |
Moderator (Huawei) |
| R1-2212812 |
[111-R16-NR] Moderator summary on UE type “SwitchedUL” and simultaneous transmission on two UL bands |
Moderator (Nokia) |
| R1-2212885 |
Draft CR on UL Tx switching for PUCCH with HARQ-ACK |
Moderator (Apple) |
| R1-2212901 |
CR on UL Tx switching for PUCCH with HARQ-ACK |
Moderator (Apple), ZTE |
| R1-2212911 |
Correction on Priority rules for CSI reports in TS 38.214 |
Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2212912 |
Correction on Priority rules for CSI reports in TS 38.214 |
Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2212913 |
Correction on UL prioritization cases related to SP-CSI in TS 38.213 |
Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2212914 |
Correction on UL prioritization cases related to SP-CSI in TS 38.213 |
Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2212915 |
Summary #3 on priority rules for CSI reports |
Moderator (Huawei) |
| R1-2213008 |
Rel-16 editorial corrections for TS 38.213 |
Samsung |
| R1-2213009 |
Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) |
Samsung |
| 8 |
Release 17 Maintenance |
|
| R1-2213010 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2213011 |
Rel-17 editorial corrections for TS 38.212 |
Huawei |
| R1-2213012 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| 8.1 |
Maintenance on Further enhancements on MIMO for NR |
|
| R1-2210944 |
Discussion on SRS closed loop power control for unified TCI |
ZTE |
| R1-2210945 |
Draft CR on SRS closed loop power control for unified TCI in TS 38.213 |
ZTE |
| R1-2210946 |
Draft CR on beam application time for unified TCI in TS 38.214 |
ZTE |
| R1-2210966 |
Discussion on the number of CSI-IM resources |
vivo |
| R1-2210967 |
Draft CR on the number of CSI-IM resources |
vivo |
| R1-2210968 |
Discussion on the SRS closed loop power control under unified TCI framework |
vivo |
| R1-2210969 |
Draft CR on the SRS closed lopp power control under unified TCI framweork |
vivo |
| R1-2211091 |
Draft CR on clarifying parameter restriction for SRS resource sets in TS 38.214 |
ZTE |
| R1-2211092 |
Draft editorial CR on SRS enhancement in TS 38.214 |
ZTE |
| R1-2211116 |
Draft CR on active BWP for beam indication |
Google |
| R1-2211117 |
Draft CR on PDCCH monitoring for intercell beam management |
Google |
| R1-2211142 |
Draft CR on aperiodic SRS enhancement in TS 38.212 |
CATT |
| R1-2211433 |
Draft CR for SRI for PUSCH repetition |
OPPO |
| R1-2211545 |
Correction on PL-RS for unified TCI framework |
Spreadtrum Communications |
| R1-2211940 |
Draft CR on UE capability name alignment of SRS antenna switching in TS 38.214 |
ZTE |
| R1-2211950 |
Draft CR on multi slot PDSCH repetition in unified TCI |
NTT DOCOMO, INC. |
| R1-2211951 |
Draft CR on HARQ-ACK for beam indication in unified TCI |
NTT DOCOMO, INC. |
| R1-2212018 |
On SRS CLPC for unified TCI framework |
Samsung |
| R1-2212081 |
Discussion of even and odd CSI subband index definition |
Qualcomm Incorporated |
| R1-2212165 |
Draft CR 38.214 Rel-17 multi-beam enhancements_beam switch HARQ |
Nokia, Nokia Shanghai Bell |
| R1-2212166 |
Discussion on Draft CR 38.214 Rel-17 multi-beam enhancements_beam switch HARQ |
Nokia, Nokia Shanghai Bell |
| R1-2212188 |
Correction on not support of simultaneous configuration of legacy TCI state and Rel-17 unified TCI state for 38.214 |
Beijing Xiaomi Electronics |
| R1-2212309 |
Correction on capability parameter name alignment for feMIMO in TS38.213 |
Sharp |
| R1-2212346 |
Draft CR on two detected DCI formats when individual PDCCH candidate overlapping with one of PDCCH repetitions |
NEC |
| R1-2212347 |
Discussion on two detected DCI formats when individual PDCCH candidate overlapping with one of PDCCH repetitions |
NEC |
| R1-2212468 |
Clarification on HARQ feedback for TCI state update indication |
Huawei, HiSilicon |
| R1-2212497 |
Draft CR to 38.214 on capability sets |
Ericsson |
| R1-2212688 |
Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management (Round 1) |
Moderator (CATT) |
| R1-2212704 |
Moderator Summary on Rel-17 FeMIMO maintenance for SRS in preparation phase |
Moderator (ZTE) |
| R1-2212716 |
Moderator Summary for Rel.17 NR FeMIMO maintenance: multi-beam |
Moderator (ZTE) |
| R1-2212717 |
Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2212767 |
Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 1 |
Moderator (ZTE) |
| R1-2212787 |
Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2212788 |
CR on PDCCH monitoring for inter-cell beam management |
Moderator (ZTE), Google, Samsung |
| R1-2212789 |
CR on beam application time for unified TCI in TS 38.214 |
Moderator(ZTE), ZTE, Google, Huawei, Nokia, Samsung |
| R1-2212790 |
Clarification on HARQ feedback for TCI state update indication |
Moderator (ZTE), Huawei, HiSilicon, Samsung |
| R1-2212791 |
Discussion related to LS on feMIMO RRC parameters |
Moderator (Ericsson) |
| R1-2212800 |
Correction on SRI for mTRP PUSCH repetition |
Moderator (Nokia), OPPO, Samsung |
| R1-2212884 |
Draft LS on feMIMO RRC parameters |
Ericsson |
| R1-2212925 |
LS on FeMIMO RRC parameters |
RAN1, Ericsson |
| R1-2212991 |
Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 2 |
Moderator (ZTE) |
| R1-2212998 |
Summary for Rel.17 NR FeMIMO maintenance: mTRP PUCCH/PUSCH enhancement |
Moderator (Nokia) |
| 8.2 |
Maintenance on Supporting NR from 52.6GHz to 71 GHz |
|
| R1-2210918 |
Remaining issues of channel access mechanism for 60 GHz unlicensed operation |
Huawei, HiSilicon |
| R1-2210970 |
Discussions on support of short control signaling in FR2-2 |
vivo |
| R1-2211156 |
Discussion on the correction for PDCCH monitoring occasion for DCI format 2_1 for the features extending NR operation to 71 GHz |
CATT |
| R1-2211157 |
Correction for PDCCH monitoring occasion for DCI format 2_1 for the features extending NR operation to 71 GHz |
CATT |
| R1-2211158 |
Discussion on the corrections of the definition of configured DL-CCs number for BD/CCE budget of scheduling cell(s) for the features extending NR operation to 71 GHz |
CATT |
| R1-2211159 |
Corrections of the definition of configured DL-CCs number for BD/CCE budget of scheduling cell(s) for the features extending NR operation to 71 GHz |
CATT |
| R1-2211160 |
Discussion on channel access procedures upon detection of a common DCI for frequency range 2-2 |
CATT |
| R1-2211161 |
Correction on channel access procedures upon detection of a common DCI for frequency range 2-2 |
CATT |
| R1-2211166 |
Discussion on the remaining issues on channel access |
CATT |
| R1-2211273 |
Clarification on Contention Exempt Short Control Signalling rules for UL in TS 37.213 |
ZTE, Sanechips |
| R1-2211274 |
Correction on cg-minDFI-Delay in FR2-2 in TS 38.213 |
ZTE, Sanechips |
| R1-2211275 |
Correction on channel measurement and interference measurement in FR2-2 in TS 38.214 |
ZTE, Sanechips |
| R1-2211379 |
Discussions on remaining issues on Channel Access for NR extension up to 71 GHz |
Intel Corporation |
| R1-2211454 |
Discussion on remaining issue for short control signaling |
OPPO |
| R1-2211455 |
Draft CR on resolving issue for short control signaling |
OPPO |
| R1-2211635 |
Discussion on last DCI determination for multi-PDSCH scheduling and single PDSCH scheduling |
ZTE |
| R1-2211944 |
Draft CR on configuration to enable LBT for msg1 and msgA |
Ericsson |
| R1-2211945 |
Discussion on configuration to enable LBT for msg1 and msgA |
Ericsson |
| R1-2211946 |
Discussion on L3-RSSI measurements and LS to RAN4 |
Ericsson |
| R1-2211947 |
Discussion on per-slot group monitoring within a duration |
Ericsson |
| R1-2211948 |
Draft CR on per-slot group monitoring within a duration |
Ericsson |
| R1-2211952 |
Discussion on remaining issues for NR in FR2-2 |
NTT DOCOMO, INC. |
| R1-2211953 |
Draft CR on channel access type for PDCCH ordered PRACH in FR2-2 |
NTT DOCOMO, INC. |
| R1-2211954 |
Draft CR on frequency hopping for PUSCH and SRS in FR2-2 |
NTT DOCOMO, INC. |
| R1-2211955 |
Draft CR on multi-PUSCH scheduling behavior alignment in FR2-2 |
NTT DOCOMO, INC. |
| R1-2211956 |
Draft CR on multi-PUSCH scheduling in unified TCI in FR2-2 |
NTT DOCOMO, INC. |
| R1-2212019 |
Discussion on SCSt based msg1/msgA transmission in FR2-2 |
Samsung |
| R1-2212082 |
Discussion Paper on Maintenance for NR from 52.6GHz to 71 GHz |
Qualcomm Incorporated |
| R1-2212083 |
Draft CR on Short Control Signaling Exemption for UL Transmissions |
Qualcomm Incorporated |
| R1-2212198 |
Correction on CSI-RS validation |
ASUSTeK |
| R1-2212295 |
Remaining issues of channel access mechanism to support NR above 52.6 GHz |
LG Electronics |
| R1-2212296 |
Draft CR on channel access type indication for DCI format x_2 in FR2-2 |
LG Electronics |
| R1-2212297 |
Draft CR on short control signaling exemption and LBT type determination within a COT |
LG Electronics |
| R1-2212395 |
Correction on short control singnling based on msg1 and msg A |
CATT |
| R1-2212396 |
Correction on UE resuming a UE initiated COT |
CATT |
| R1-2212403 |
Remaining issues on channel access mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2212404 |
Correction on Short Control Signaling |
Nokia, Nokia Shanghai Bell |
| R1-2212405 |
Correction on UE resuming a UE initiated COT |
Nokia, Nokia Shanghai Bell |
| R1-2212434 |
FL Summary for B52.6 GHz PDCCH monitoring enhancements |
Moderator (Lenovo) |
| R1-2212435 |
Remaining issue on channel access for NR from 52.6GHz to 71GHz |
WILUS Inc. |
| R1-2212436 |
Draft CR on channel access after failure of Type 2 channel access for FR2-2 |
WILUS Inc. |
| R1-2212437 |
Draft CR on channel access procedure upon detection of a common DCI for FR2-2 |
WILUS Inc. |
| R1-2212469 |
Corrections to multi beam channel access in TS37.213 |
Huawei, HiSilicon |
| R1-2212470 |
Corrections to enable/disable short control signaling transmission in TS37.213 |
Huawei, HiSilicon |
| R1-2212471 |
Corrections to support LBT upgrade to Type 2/3 within gNB COT in TS37.213 |
Huawei, HiSilicon |
| R1-2212585 |
Preparation phase discussion summary for FR2-2 maintenance |
Moderator (Qualcomm) |
| R1-2212586 |
FL summary for channel access mechanism of FR2-2 maintenance, ver 01 |
Moderator (Qualcomm) |
| R1-2212587 |
FL summary for channel access mechanism of FR2-2 maintenance, ver 02 |
Moderator (Qualcomm) |
| R1-2212588 |
Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| R1-2212740 |
Discussion Summary #1 of Beam Management for New SCSs |
Moderator (InterDigital, Inc.) |
| R1-2212763 |
Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| R1-2212764 |
CR on frequency hopping for PUSCH and SRS in FR2-2 |
Moderator (LG Electronics), NTT DOCOMO, Ericsson |
| R1-2212818 |
Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| R1-2212826 |
[Draft] LS to RAN4 on L3-RSSI measurement for NR up to 71GHz |
Qualcomm |
| R1-2212830 |
LS to RAN4 and RAN2 on L3-RSSI measurement for NR up to 71GHz |
RAN1, Qualcomm |
| R1-2212832 |
Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) |
Ad-Hoc Chair (Huawei) |
| R1-2212853 |
Corrections of the definition of configured DL-CCs number for BD/CCE budget of scheduling cell(s) for the features extending NR operation to 71 GHz |
CATT |
| R1-2212854 |
CR on per-slot group monitoring within a duration |
Ericsson |
| R1-2212907 |
Correction of number of configured DL-CCs for BD/CCE budget for FR2-2 |
Moderator (Lenovo), CATT |
| R1-2212908 |
Correction on per-slot group monitoring within a duration for FR2-2 |
Moderator (Lenovo), Ericsson |
| R1-2212951 |
Draft LS to RAN2 on msg1/msgA transmission channel access control in SIB1 |
Moderator (Qualcomm) |
| R1-2212952 |
Draft CR to 37.213 on msg1/msgA transmission channel access control |
Moderator (Qualcomm) |
| R1-2212964 |
Draft LS to RAN2 on msg1/msgA transmission channel access control in SIB1 |
Moderator (Qualcomm) |
| R1-2212965 |
LS to RAN2 on msg1/msgA transmission channel access control in SIB1 |
RAN1, Qualcomm |
| R1-2212979 |
Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| 8.3 |
Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC |
|
| R1-2210861 |
Correction on PUCCH cell switching in 38.213 |
Huawei, HiSilicon |
| R1-2210971 |
Correction on triggering of enhanced Type-3 codebook in TS38.213 |
vivo |
| R1-2211257 |
Correction on sub-slot based HARQ-ACK transmission for PUCCH cell switching |
CATT |
| R1-2211260 |
Correction on sub-slot based HARQ-ACK transmission for PUCCH cell switching |
CATT |
| R1-2211278 |
Editorial correction on UE initiated semi-static channel access parameters in TS 38.212 |
ZTE, Sanechips |
| R1-2211279 |
Editorial correction on UE initiated semi-static channel access parameters in TS 38.214 |
ZTE, Sanechips |
| R1-2211493 |
Draft CR on joint operation of Rel-17 intra-UE multiplexing and SPS HARQ deferral |
OPPO |
| R1-2211519 |
Correction on sub-slot description for UCI transmission |
CATT |
| R1-2211636 |
Draft CR on PUCCH transmission after multiplexing UCI with different priorities |
ZTE |
| R1-2212084 |
Correction on UE procedure for reporting HARQ-ACK with PUCCH cell switch |
Qualcomm Incorporated |
| R1-2212085 |
Correction on 4-bit subband CQI feedback |
Qualcomm Incorporated |
| R1-2212310 |
Corrections on RRC parameter name alignment for IIOT in TS38.213 |
Sharp |
| R1-2212455 |
Correction on RRC parameters in 38.213 |
Huawei, HiSilicon |
| R1-2212456 |
Correction on RRC parameters in 38.214 |
Huawei, HiSilicon |
| R1-2212479 |
Correction on UCI reporting at PUSCH in 38.213 |
Huawei, HiSilicon |
| R1-2212746 |
Summary#1 on intra-UE multiplexing/prioritization B |
Moderator (OPPO) |
| R1-2212747 |
Draft CR on PUCCH transmission after multiplexing UCI with different priorities |
Moderator (OPPO), ZTE, Huawei, HiSilicon |
| R1-2212794 |
Moderator summary #1 on Maintenance NR Rel-17 URLLC/IIoT: HARQ-ACK feedback enhancements & RRC parameter alignment |
Moderator (Nokia) |
| R1-2212795 |
Correction on triggering of enhanced Type-3 codebook |
Moderator (Nokia), vivo |
| R1-2212796 |
Correction on PUCCH cell switching |
Moderator (Nokia), CATT, Huawei, HiSilicon, Qualcomm |
| R1-2212797 |
[Draft] LS on Rel-17 URLLC/IIoT RRC parameter update |
Moderator (Nokia) |
| R1-2212810 |
Correction on HARQ-ACK reporting on PUSCH for Rel-17 Intra-UE multiplexing |
Moderator (Nokia), Huawei, HiSilicon |
| R1-2212833 |
Session notes for 8.3 (Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC) |
Ad-hoc Chair (CMCC) |
| R1-2212880 |
Correction on triggering of enhanced Type-3 codebook |
Moderator (Nokia), vivo |
| R1-2212881 |
Correction on PUCCH cell switching |
Moderator (Nokia), CATT, Huawei, HiSilicon, Qualcomm |
| R1-2212882 |
Correction on HARQ-ACK reporting on PUSCH for Rel-17 Intra-UE multiplexing |
Moderator (Nokia), Huawei, HiSilicon |
| R1-2212883 |
Final Moderator summary on Maintenance NR Rel-17 URLLC/IIoT: HARQ-ACK feedback enhancements & RRC parameter alignment |
Moderator (Nokia) |
| 8.4 |
Maintenance on Solutions for NR to support non-terrestrial networks (NTN) |
|
| R1-2210870 |
Discussion on UE backward propagation of the ephemaris and common TA |
Huawei, HiSilicon |
| R1-2211456 |
Draft CR on correction for UE performing pre-compensation |
OPPO, Apple |
| R1-2212311 |
Corrections on RRC parameter name alignment for NR NTN in TS38.213 |
Sharp |
| R1-2212313 |
On epoch time and validity of assistance information for R17 NR NTN |
Ericsson |
| R1-2212399 |
Remaining aspects of Rel-17 maintenance for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2212400 |
Draft CR for 38.213 to clarify calculation and application of timing advance values for common TA and UE specific TA |
Nokia, Nokia Shanghai Bell |
| R1-2212613 |
FL Summary #1: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2212614 |
FL Summary #2: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2212615 |
FL Summary #3: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2212616 |
FL Summary #4: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2212774 |
Discussion on reply to RAN2 LS on validity of assistance information |
Moderator (OPPO) |
| R1-2212808 |
[Draft] reply LS on validity of assistance information |
OPPO |
| R1-2212834 |
Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) |
Ad-Hoc Chair (Huawei) |
| R1-2212929 |
[Draft] reply LS on validity of assistance information |
OPPO |
| R1-2212958 |
Reply LS on validity of assistance information |
RAN1, OPPO |
| R1-2212984 |
Reply LS on validity of assistance information |
RAN1, OPPO |
| 8.5 |
Maintenance on NR Positioning Enhancements |
|
| R1-2210899 |
Remaining issues of Rel-17 positioning enhancements |
Huawei, HiSilicon |
| R1-2211162 |
Correction on configuration of UE Tx TEG association information reporting |
CATT |
| R1-2211163 |
Discussion on configuration of UE Tx TEG association information reporting |
CATT |
| R1-2211308 |
Maintenance of NR Positioning Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2211309 |
Correction on PRS RSTD and PRS RSRPP reporting |
Nokia, Nokia Shanghai Bell |
| R1-2211310 |
Correction on DL PRS priority states in PPW |
Nokia, Nokia Shanghai Bell |
| R1-2211498 |
Draft CR on priority issue in PPW |
ZTE |
| R1-2211499 |
Draft CR on UE TEG margin value report |
ZTE |
| R1-2212020 |
Discussion on PRS collision handling for UL signals in PPW |
Samsung |
| R1-2212021 |
Draft CR for PRS collision handling for UL signals in PPW |
Samsung |
| R1-2212466 |
Corrections on parameters for NR positioning |
Huawei, HiSilicon |
| R1-2212494 |
Corrections on UE behaviour of other DL signals and channels |
Huawei, HiSilicon |
| R1-2212495 |
Corrections on N2 symbols on the collision action timeline |
Huawei, HiSilicon |
| R1-2212502 |
Maintenance for NR positioning enhancements |
Ericsson |
| R1-2212503 |
draft CR for maintenance of NR positioning enhancements |
Ericsson |
| R1-2212544 |
FL Summary for mitigating UE/gNB Rx/Tx timing delays |
Moderator (CATT) |
| R1-2212600 |
Feature lead summary for maintenance of NR positioning enhancements |
Moderator (Ericsson) |
| R1-2212604 |
Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation |
Moderator (Nokia) |
| R1-2212729 |
Summary #1 of positioning latency improvements and RRC_INACTIVE positioning |
Moderator (Huawei) |
| R1-2212730 |
Summary #2 of positioning latency improvements and RRC_INACTIVE positioning |
Moderator (Huawei) |
| R1-2212731 |
Corrections on parameters for NR positioning |
Moderator (Huawei) |
| R1-2212752 |
[Draft] CR on UE TEG margin value report |
Moderator (CATT), ZTE, Ericsson |
| R1-2212753 |
CR on UE TEG margin value report |
Moderator (CATT), ZTE, Ericsson |
| R1-2212754 |
Correction on configuration of UE Tx TEG association information reporting |
Moderator (CATT), CATT |
| R1-2212835 |
Session notes for 8.5 (Maintenance on NR Positioning Enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2212867 |
Correction on DL PRS priority states in PPW |
Moderator (Huawei), Nokia, Nokia Shanghai Bell |
| R1-2212868 |
Correction on DL PRS priority states in PPW |
Moderator (Huawei), Nokia, Nokia Shanghai Bell |
| R1-2212869 |
Correction on PRS processing during RACH procedure |
Moderator (Huawei), ZTE |
| 8.6 |
Maintenance on Support of Reduced Capability NR Devices |
|
| R1-2210972 |
Correction for RedCap SDT operation in separate initial BWP |
vivo |
| R1-2211329 |
Discussion on physical layer aspects of small data transmission |
xiaomi |
| R1-2211841 |
On clarifications for Msg1/MsgA retransmission timeline |
Nokia, Nokia Shanghai Bell |
| R1-2211874 |
Remaining details of Rel-17 RedCap UE |
NEC |
| R1-2211899 |
Discussion on RedCap remaining issues |
ZTE, Sanechips |
| R1-2211900 |
Correction on TDRA misalignment of PUSCH for RedCap |
ZTE, Sanechips |
| R1-2211957 |
Draft CR on collision between DL transmission and NCD-SSB |
NTT DOCOMO, INC. |
| R1-2211958 |
Discussion on corrections and clarifications for RedCap UE |
NTT DOCOMO, INC. |
| R1-2212086 |
Remaining Issues on Procedures of RedCap UE |
Qualcomm Incorporated |
| R1-2212245 |
On RedCap remaining issues |
MediaTek Inc. |
| R1-2212409 |
Msg1/MsgA retransmission timeline for RedCap UEs |
Ericsson |
| R1-2212485 |
Remaining issues on paging monitoring and measurement during SDT procedure for RedCap |
Huawei, HiSilicon |
| R1-2212530 |
FL summary #1 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2212531 |
FL summary #2 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2212532 |
FL summary #3 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2212836 |
Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) |
Ad-hoc Chair (CMCC) |
| R1-2212980 |
FL summary #4 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2212981 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| 8.7 |
Maintenance on UE Power Saving Enhancements |
|
| R1-2210862 |
Correction on the short message indicator when TRS availability indication is present |
Huawei, HiSilicon |
| R1-2210973 |
Correction on PDCCH monitoring adaptation and BWP switching |
vivo |
| R1-2210974 |
Correction on mixed R16 SSSG switching and R17PDCCH monitoring adaptation |
vivo |
| R1-2211330 |
Remaining issues of PDCCH monitoring adaptation for power saving |
xiaomi |
| R1-2211331 |
UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI |
xiaomi |
| R1-2211468 |
Draft CR for power saving and BWP adaptation |
OPPO |
| R1-2211901 |
Correction on inconsistent PDCCH monitoring indication |
ZTE, Sanechips |
| R1-2212151 |
Miscellaneous corrections for alignment CR for UE power savings |
Ericsson |
| R1-2212152 |
Correction for 38.213 on PDCCH monitoring adaptation field in a DCI indicating BWP change |
Ericsson |
| R1-2212153 |
Correction for 38.213 on PDCCH monitoring adaptation field |
Ericsson |
| R1-2212280 |
Open issues on PDCCH monitoring adaptation for UE power saving |
Nokia, Nokia Shanghai Bell |
| R1-2212281 |
Alignment of PDCCH monitoring adaptation behaviour and BWP switching |
Nokia, Nokia Shanghai Bell |
| R1-2212457 |
Correction on PDCCH monitoring adaptation and BWP switching |
Huawei, HiSilicon |
| R1-2212813 |
Summary#1 for maintenance on UE power saving enhancements |
Moderator (MediaTek Inc.) |
| R1-2212837 |
Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) |
Ad-hoc Chair (CMCC) |
| R1-2212902 |
Correction on PDCCH monitoring adaptation and BWP switching |
Moderator (MediaTek), vivo |
| R1-2212903 |
Correction on the short message indicator when TRS availability indication is present |
Moderator (MediaTek), Huawei, HiSilicon, Ericsson |
| R1-2213002 |
Summary#2 for maintenance on UE power saving enhancements |
Moderator (MediaTek Inc.) |
| 8.8 |
Maintenance on NR coverage enhancement |
|
| R1-2210975 |
Correction of RV of CG PUSCH repetitions |
vivo |
| R1-2211469 |
Draft CR for restarting DMRS bundling |
OPPO |
| R1-2211637 |
Correction on restarting of DMRS bundling |
ZTE |
| R1-2211638 |
Correction on the gap between two consecutive UL transmissions for DMRS bundling |
ZTE |
| R1-2211639 |
Discussion on DMRS bundling during DAPS handover |
ZTE |
| R1-2211640 |
Draft CR on DMRS bundling during DAPS handover |
ZTE |
| R1-2211959 |
Discussion on remaining issues for NR coverage enhancement |
NTT DOCOMO, INC. |
| R1-2212176 |
Corrections on DMRS bundling for PUCCH transmission for reduced capability HD-UE |
Sharp |
| R1-2212177 |
Corrections on determination N·K for DMRS bundling of CS-PUSCH |
Sharp |
| R1-2212413 |
Discussion on Power Control with DMRS Bundling |
Ericsson |
| R1-2212414 |
Correction for Power Control with DMRS Bundling |
Ericsson |
| R1-2212461 |
Correction on determining additional DM-RS for Msg3 with frequency hopping enabled/disabled |
Huawei, HiSilicon |
| R1-2212584 |
FL summary of discussion on joint channel estimation for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2212766 |
FL summary of remaining issues for TB processing over multi-slot PUSCH |
Moderator (Nokia) |
| R1-2212838 |
Session notes for 8.8 (NR coverage enhancement) |
Ad-hoc Chair (CMCC) |
| R1-2212856 |
Correction of RV of CG PUSCH repetitions |
Moderator (Nokia), vivo |
| R1-2212857 |
Correction of RV of CG PUSCH repetitions |
Moderator (Nokia), vivo |
| R1-2212871 |
Draft Correction on events for restarting of DMRS bundling |
Moderator (China Telecom), ZTE |
| R1-2212872 |
Draft Correction on DMRS bundling for reduced capability HD-UE |
Moderator (China Telecom), Sharp |
| R1-2212873 |
Draft Correction on determination N·K for DMRS bundling of CG-PUSCH |
Moderator (China Telecom), Sharp |
| R1-2212874 |
Correction on events for restarting of DMRS bundling |
Moderator (China Telecom), ZTE |
| R1-2212875 |
Correction on DMRS bundling for reduced capability HD-UE |
Moderator (China Telecom), Sharp |
| R1-2212876 |
Correction on determination N·K for DMRS bundling of CG-PUSCH |
Moderator (China Telecom), Sharp |
| R1-2212959 |
Correction on events for restarting of DMRS bundling |
Moderator (China Telecom), ZTE |
| R1-2212960 |
Correction on DMRS bundling for reduced capability HD-UE |
Moderator (China Telecom), Sharp |
| R1-2212961 |
Correction on determination N·K for DMRS bundling of CG-PUSCH |
Moderator (China Telecom), Sharp |
| 8.9 |
Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC |
|
| R1-2211768 |
DRAFT CR On the no acquisition of the repetition number via DCI for 16-QAM transmissions in NB-IoT |
Ericsson |
| R1-2211769 |
On the no repetition number acquisition via DCI for 16-QAM in NB-IoT |
Ericsson |
| R1-2212748 |
Feature lead summary on 111-R17-NB_IoT_MTC |
Moderator (Huawei) |
| R1-2212839 |
Session notes for 8.9 (Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC) |
Ad-hoc Chair (CMCC) |
| R1-2212976 |
Correction on repetition number acquisition for NPDSCH and NPUSCH with 16-QAM |
Moderator (Huawei) |
| R1-2212977 |
Correction on repetition number acquisition for NPDSCH and NPUSCH with 16-QAM |
Moderator (Huawei), Ericsson, Lenovo, Huawei, HiSilicon |
| 8.10 |
Maintenance on Enhancements to Integrated Access and Backhaul |
|
| R1-2211305 |
Correction on RB set size for Rel-17 IAB FDM multiplexing |
Nokia, Nokia Shanghai Bell |
| R1-2212022 |
Maintenance on Enhancements to NR IAB |
Samsung |
| R1-2212087 |
Draft CR on correction on RB set size for Rel-17 IAB FDM |
Qualcomm Incorporated |
| R1-2212200 |
Correction on RB set size for an IAB-DU cell |
ZTE, Sanechips |
| R1-2212201 |
Correction on DL TX power adjustment for eIAB in TS 38.213 |
ZTE, Sanechips |
| R1-2212338 |
Draft CR on DL Tx power control |
Ericsson |
| R1-2212339 |
Discussion on DL Tx power control |
Ericsson |
| R1-2212340 |
Draft CR on RB set size |
Ericsson |
| R1-2212341 |
Maintenance on enhanced IAB |
Ericsson |
| R1-2212481 |
Remaining issues on resource multiplexing for IAB |
Huawei, HiSilicon |
| R1-2212482 |
Correction on coexistence between Rel-16 and Rel-17 H/S/NA configuration |
Huawei, HiSilicon |
| R1-2212804 |
Feature lead summary for Maintenance on eIAB |
Moderator (Ericsson) |
| R1-2212939 |
Correction on RB set size for Rel-17 IAB HSNA configuration |
Moderator (Ericsson), ZTE, Sanechips, Nokia, NSB, Samsung, Lenovo, Huawei, HiSilicon |
| R1-2212940 |
Correction on DL TX power adjustment for Rel-17 IAB |
Moderator (Ericsson), ZTE, Sanechips, Samsung, Lenovo, Huawei, HiSilicon |
| 8.11 |
Maintenance on NR Sidelink enhancement |
|
| R1-2210838 |
Discussion on correction for inter-UE coordination Scheme 2 determination of UE-B |
FUTUREWEI |
| R1-2210895 |
Correction on power control for PSCCH/PSSCH/PSFCH/S-SSB in TS 38.213 |
Huawei, HiSilicon |
| R1-2210896 |
Correction on Q formula in step 6 of sensing and resource exclusion procedure in TS 38.214 |
Huawei, HiSilicon |
| R1-2210976 |
Correction on Q formula in sensing and resource exclusion procedure |
vivo |
| R1-2210977 |
Clarification of the sensing occasions for periodic-based partial sensing |
vivo |
| R1-2210978 |
Clarification on IUC related transmission based on latency bound |
vivo |
| R1-2210979 |
Correction for SL power control parameters |
vivo |
| R1-2211143 |
Correction on the operations of partial sensing |
CATT, GOHIGH |
| R1-2211144 |
Correction on resource exclusion behavior with non-preferred resource set |
CATT, GOHIGH |
| R1-2211145 |
Discussion on resource exclusion behavior with non-preferred resource set |
CATT, GOHIGH |
| R1-2211262 |
Clarification on cast type for IUC scheme 1 |
LG Electronics |
| R1-2211442 |
Draft CR on Q formula in step 6c for periodic-based partial sensing |
OPPO |
| R1-2211443 |
Draft CR on starting slot and pre-condition in re-evaluation and pre-emption checking for partial sensing |
OPPO |
| R1-2211444 |
Draft CR on contiguous partial sensing window in SL DRX inactive time |
OPPO |
| R1-2211445 |
Draft CR on UE procedure for determining a resource conflict |
OPPO |
| R1-2211584 |
Draft CR on re-evaluation and pre-emption checking for partial sensing |
Lenovo |
| R1-2211793 |
Correction on Q formula for the second most recent periodic sensing occasion |
Apple |
| R1-2211794 |
Correction on CPS monitoring length during sidelink DRX inactive time |
Apple |
| R1-2211795 |
Correction on determining UE-B among UEs scheduling conflicting TBs |
Apple |
| R1-2211852 |
Clarification on monitoring slots for pre-emption check due to half-duplex constraint in partial sensing |
Sharp |
| R1-2211853 |
Clarification on Preserve for periodic based partial sensing |
Sharp |
| R1-2211854 |
Clarification on candidate slots for aperiodic transmission in partial sensing |
Sharp |
| R1-2211855 |
Clarification on determination of preferred resource set for IUC scheme 1 |
Sharp |
| R1-2211960 |
Draft CR on condition to be UE-A for SL IUC scheme 2 |
NTT DOCOMO, INC. |
| R1-2211961 |
Draft CR on half-duplex consideration for SL re-evaluation/pre-emption check |
NTT DOCOMO, INC. |
| R1-2211962 |
Draft CR on insufficient candidate resources for SL re-evaluation/pre-emption check |
NTT DOCOMO, INC. |
| R1-2211963 |
Draft CR on slot n+T3 excluded from SL re-evaluation/pre-emption check |
NTT DOCOMO, INC. |
| R1-2211964 |
Draft CR on removal of duplicated spec description on IUC scheme 2 |
NTT DOCOMO, INC. |
| R1-2211965 |
Discussion on RAN2-related topics for SL maintenance |
NTT DOCOMO, INC. |
| R1-2212088 |
Draft CR on Non-preferred Resources |
Qualcomm Incorporated |
| R1-2212089 |
Draft CR on Power Control Parameters |
Qualcomm Incorporated |
| R1-2212202 |
Correction to the Q formula in Step 6 of mode 2 partial sensing procedure |
ZTE, Sanechips |
| R1-2212203 |
Corrections to Re-evaluation and Pre-emption Checking for Partial Sensing |
ZTE, Sanechips |
| R1-2212204 |
Correction on Condition 2-A-1 of IUC scheme 1 |
ZTE, Sanechips |
| R1-2212205 |
Clarification on UE procedure for receiving PSFCH with conflict information |
ZTE, Sanechips |
| R1-2212217 |
[Draft] Clarification on valid PSFCH occasions for resource conflict information |
Ericsson |
| R1-2212218 |
[Draft] Consideration of associated processing times for contiguous partial sensing |
Ericsson |
| R1-2212219 |
[Draft] Correction to contiguous partial sensing window |
Ericsson |
| R1-2212220 |
[Draft] Modifications on SL open loop power control formulae |
Ericsson |
| R1-2212447 |
Corrections for SL Inter-UE coordination |
Nokia, Nokia Shanghai Bell |
| R1-2212463 |
Correction on description of random resource selection in TS 38.214 |
Huawei, HiSilicon |
| R1-2212464 |
Correction on UE-A is the destination UE of a TB transmitted by UE-B in TS 38.214 |
Huawei, HiSilicon |
| R1-2212465 |
Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 |
Huawei, HiSilicon |
| R1-2212597 |
Feature lead summary #1 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2212598 |
Feature lead summary #2 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2212599 |
Feature lead summary #3 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2212677 |
FL summary #1 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2212678 |
FL summary #2 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2212679 |
FL summary #3 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2212680 |
FL summary for AI 8.11: R17 eSL power saving RA maintenance (EOM) |
Moderator (OPPO) |
| R1-2212820 |
Feature lead summary #4 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2212821 |
Draft LS on cast types for IUC scheme 1 |
Moderator (LG Electronics) |
| R1-2212822 |
LS on cast types for IUC scheme 1 |
RAN1, LG Electronics |
| R1-2212823 |
Correction on duplicated part on UE procedure for determining a resource conflict between TS 38.213 and TS 38.214 |
Moderator (LG Electronics) |
| R1-2212824 |
Correction on description of valid PSFCH occasion for Scheme 2 |
Moderator (LG Electronics) |
| R1-2212825 |
Correction on SL open loop power control parameters |
Moderator (LG Electronics) |
| R1-2212840 |
Session notes for 8.11 (Maintenance on NR Sidelink enhancement) |
Ad-Hoc Chair (Huawei) |
| R1-2212906 |
Correction on UE procedure for receiving PSFCH with conflict information |
Moderator (LG Electronics) |
| R1-2212955 |
Correction on the Q formula for periodic-based partial sensing |
Moderator (OPPO) |
| R1-2212956 |
Correction on the re-evaluation and pre-emption checking for periodic and aperiodic transmissions |
Moderator (OPPO) |
| R1-2212989 |
Correction on duplicated part on UE procedure for determining a resource conflict between TS 38.213 and TS 38.214 |
Moderator (LG Electronics), Samsung, ZTE, Sanechips, Nokia, Nokia Shanghai Bell, NTT DOCOMO, OPPO, Ericsson, Huawei, HiSilicon |
| R1-2212990 |
Correction on SL open loop power control parameters |
Moderator (LG Electronics), Samsung, vivo, ZTE, Sanechips, Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, Huawei, HiSilicon |
| R1-2212992 |
Correction on the re-evaluation and pre-emption checking for periodic and aperiodic transmissions |
Moderator (OPPO), Huawei, HiSilicon, Samsung, LG Electronics, Ericsson, ZTE, Sanechips, vivo, Lenovo, NTT DOCOMO, CMCC |
| 8.12 |
Maintenance on NR Multicast and Broadcast Services |
|
| R1-2210863 |
Correction on PUCCH resource determination of multicast HARQ-ACK |
Huawei, HiSilicon, CBN, Nokia, Nokia Shanghai Bel |
| R1-2210864 |
Correction on multiplexing HARQ-ACK for DG and SPS multicast and unicast |
Huawei, HiSilicon, CBN |
| R1-2210865 |
Correction on PRI for NACK-only HARQ-ACK feedback to TS38.213 |
Huawei, HiSilicon, CBN |
| R1-2210866 |
Correction on interpretation of moreThanOneNackOnlyMode |
Huawei, HiSilicon, CBN |
| R1-2210867 |
Correction on retransmission schemes for MBS HARQ-ACK feedback to TS38.213 |
Huawei, HiSilicon, CBN |
| R1-2210980 |
Draft CR on multiplexing HARQ-ACK for DG and SPS multicast and unicast |
vivo |
| R1-2210981 |
Correction on PUCCH determination for NACK only mode 1 for SPS PDSCH |
vivo |
| R1-2210982 |
Draft CR on deleting redundant descriptions for NACK only PUCCH transmission |
vivo |
| R1-2210983 |
Draft CR on PUCCH determination for NACK-only HARQ-ACK feedback to TS38.213 |
vivo |
| R1-2210984 |
Draft CR on PUCCH resources for SPS PDSCHs with NACK only feedback mode |
vivo |
| R1-2210985 |
Draft CR on FDM unicast PDSCH and multicast PDSCH to TS38.214 |
vivo |
| R1-2211040 |
Discussion on overlapping of NACK only PUCCH and SR PUCCH |
vivo |
| R1-2211146 |
Discussion on MBS supporting HARQ-ACK codebook retransmission |
CATT |
| R1-2211147 |
Discussion on MBS supporting deferring HARQ-ACK for SPS PDSCH |
CATT |
| R1-2211148 |
Draft CR on MBS supporting HARQ-ACK codebook retransmission |
CATT |
| R1-2211149 |
Draft CR on MBS supporting deferring HARQ-ACK for SPS PDSCH |
CATT |
| R1-2211150 |
Discussion on format 4_0/4_1 DCI size alignment to CSS format 1_0 |
CATT |
| R1-2211151 |
Draft CR on format 4_0 DCI size alignment to CSS format 1_0 |
CATT |
| R1-2211152 |
Draft CR on format 4_1 DCI size alignment to CSS format 1_0 |
CATT |
| R1-2211153 |
Draft CR on configuration limitation of DCI size DCI format 4_2 |
CATT |
| R1-2211154 |
Correction on UL DAI applying to G-CS-RNTI DAI counting |
CATT |
| R1-2211155 |
Draft editorial CR on DCI format 4_2 |
CATT |
| R1-2211641 |
Maintenance of broadcast and multicast for MBS |
ZTE |
| R1-2211642 |
Draft CR on PUCCH determination for NACK-only mode 1 with one bit |
ZTE |
| R1-2211643 |
Draft CR on NACK-only mode 1 and mode 2 with more than one bits |
ZTE |
| R1-2211644 |
Draft CR on multiplexing for the different HARQ-ACK reporting modes |
ZTE |
| R1-2211645 |
Draft CR on the NACK-only mode 1 |
ZTE |
| R1-2211646 |
Draft 212 CR on terms of G-RNTI |
ZTE |
| R1-2211647 |
Draft 213 CR on terms of G-RNTI |
ZTE |
| R1-2211648 |
Draft 214 CR on terms of G-RNTI |
ZTE |
| R1-2211649 |
Draft 214 CR on FDM reception |
ZTE |
| R1-2211650 |
Draft CR on the Type-3 codebook for MBS |
ZTE |
| R1-2211651 |
Draft CR on intra-UE multiplexing with NACK-only PUCCH |
ZTE |
| R1-2211656 |
Draft CR on MCCH change notification |
CMCC |
| R1-2211657 |
Draft CR on multiple G-RNTIs for NACK-only feedback mode 2 |
CMCC |
| R1-2211658 |
Draft CR on broadcast search space monitoring occasion determination |
CMCC |
| R1-2211659 |
Clarification of FDMed unicast PDSCH and group-common PDSCH capability |
CMCC |
| R1-2211660 |
Draft CR on FDMed unicast PDSCH and group-common PDSCH |
CMCC |
| R1-2211661 |
Draft CR on SPS and dynamic scheduling PDSCH(s) collision for MBS |
CMCC |
| R1-2211662 |
Draft CR on terms of MTCH used in TS 38.213 |
CMCC |
| R1-2211663 |
Draft CR on terms of MTCH used in TS 38.214 |
CMCC |
| R1-2211844 |
Remaining Issues for RRC_CONNECTED UEs supporting MBS |
Nokia, Nokia Shanghai Bell |
| R1-2211847 |
Draft CR on NACK-only HARQ-ACK feedback Mode 1 Single TB Operation to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2211848 |
Draft CR on NACK-only HARQ-ACK feedback Mode 2 for Multiple G-RNTIs to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2211849 |
Draft CR on Counting and Ordering of HARQ-ACK bits for NACK-only Feedback Mode 2 to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2211966 |
Draft CR on NACK-only based feedback when multiple G-RNTIs are configured |
NTT DOCOMO, INC. |
| R1-2211967 |
Draft CR on NACK-only based HARQ-ACK feedback mode 2 |
NTT DOCOMO, INC. |
| R1-2212023 |
Maintenance on multicast-broadcast services |
Samsung |
| R1-2212090 |
Remaining issues for NR MBS |
Qualcomm Incorporated |
| R1-2212091 |
Draft CR on PDSCH processing time required to select PUCCH for NACK-only mode2 based multicast feedback |
Qualcomm Incorporated |
| R1-2212092 |
Draft CR on multicast PDSCH with a HARQ process with disabled HARQ-ACK feedback |
Qualcomm Incorporated |
| R1-2212093 |
Draft CR on G-RNTI/G-CS-RNTI not configured with harq-FeedbackEnablerMulticast |
Qualcomm Incorporated |
| R1-2212094 |
Darft CR on Type-2 codebook generation of DG and SPS multicast |
Qualcomm Incorporated |
| R1-2212095 |
Draft CR on NACK-only mode 2 multicast feedback |
Qualcomm Incorporated |
| R1-2212189 |
Correction on Type-3 HARQ-ACK codebook for NACK-only mode in MBS |
Langbo |
| R1-2212264 |
Correction on processing procedure timeline for MBS multicast NACK only mode 2 to TS38.214 |
MediaTek Inc. |
| R1-2212265 |
Correction on RM pattern for MBS broadcast reception to TS38.214 |
MediaTek Inc. |
| R1-2212266 |
Correction on PRI for NACK-only HARQ-ACK feedback to TS 38.213 |
MediaTek Inc. |
| R1-2212267 |
Remaining issues on NR MBS |
MediaTek Inc. |
| R1-2212298 |
Draft CR on multicast HARQ-ACK |
LG Electronics |
| R1-2212299 |
Draft CR on NR MBS |
LG Electronics |
| R1-2212324 |
Correction on first SPS PDSCH |
ASUSTeK |
| R1-2212357 |
Remaining Issues on NR MBS |
NEC |
| R1-2212373 |
Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2212388 |
Draft CR on DAI update for multicast DCI formats and Type-2 HARQ-ACK codebook |
Lenovo |
| R1-2212389 |
Draft CR on HARQ-ACK codebook generation for RRC disabled HARQ-ACK feedback |
Lenovo |
| R1-2212390 |
Draft CR on processing timeline for NACK-only mode 2 for multicast |
Lenovo |
| R1-2212391 |
Remaining issues on HARQ-ACK feedback for NR MBS |
Lenovo |
| R1-2212406 |
Correction on RRC based disabled and HARQ-ACK CB generation to TS 38.213 |
MediaTek Beijing Inc. |
| R1-2212458 |
Remaining issues for Rel-17 MBS |
Huawei, HiSilicon, CBN |
| R1-2212459 |
Correction on processing timeline for NACK-only mode2 to TS38.214 |
Huawei, HiSilicon, CBN |
| R1-2212460 |
Draft LS to RAN2 on correcting interpretation of moreThanOneNackOnlyMode |
Huawei, HiSilicon |
| R1-2212504 |
draft CR to 38.214 for the NACK only timeline |
Ericsson |
| R1-2212505 |
draft CR to 38.213 for NACK only mode 2 configuration with multiple G-RNTI |
Ericsson |
| R1-2212506 |
draft CR to 38.213 for NACK only mode 2 configuration |
Ericsson |
| R1-2212507 |
draft CR to 38.213 for PTP retransmissions of PTM |
Ericsson |
| R1-2212508 |
draft CR to 38.213 for HARQ process enabling for MBS |
Ericsson |
| R1-2212509 |
draft CR to 38.214 on DCI for enable/disable HARQ for MBS |
Ericsson |
| R1-2212510 |
draft CR to 38.214 for FDM SPS collision handling for MBS |
Ericsson |
| R1-2212511 |
Maintenance on NR Multicast and Broadcast Services |
Ericsson |
| R1-2212618 |
FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2212619 |
FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2212620 |
FLS#3 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2212621 |
FLS#4 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2212622 |
Draft CR on interpretation of moreThanOneNackOnlyMode |
Moderator (Huawei) |
| R1-2212623 |
Draft CR on PRI for NACK-only HARQ-ACK feedback to TS38.213 |
Moderator (Huawei) |
| R1-2212624 |
Draft CR on processing timeline for NACK-only mode2 to TS38.214 |
Moderator (Huawei), HiSilicon, CBN |
| R1-2212625 |
Draft CR on PUCCH resource determination of multicast HARQ-ACK |
Moderator (Huawei), HiSilicon, CBN, Nokia, Nokia Shanghai Bell, ZTE, Samsung |
| R1-2212626 |
Draft CR on multiplexing HARQ-ACK for DG and SPS multicast and unicast |
Moderator (Huawei), HiSilicon, CBN, vivo, Samsung, Qualcomm |
| R1-2212627 |
Draft CR on HARQ-ACK codebook generation for RRC disabled HARQ-ACK feedback |
Moderator (Huawei), Lenovo, Samsung, MediaTek |
| R1-2212628 |
Draft CR on not applying disabled HARQ-ACK to multicast SPS PDSCH without PDCCH scheduling |
Moderator (Huawei), Qualcomm Incorporated, ASUSTeK |
| R1-2212629 |
Draft CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated |
| R1-2212630 |
Draft CR on PUCCH resources for SPS PDSCHs with NACK only feedback mode |
Moderator (Huawei), vivo |
| R1-2212631 |
Draft CR on alignment of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, vivo, ZTE |
| R1-2212632 |
Draft CR on NACK-only mode1 applies to more than one G-RNTI |
Moderator (Huawei) |
| R1-2212633 |
Draft CR on applying NACK-only mode 2 to more than one G-RNTI |
Moderator (Huawei) |
| R1-2212634 |
Draft CR on retransmission schemes for MBS HARQ-ACK feedback to TS38.213 |
Moderator (Huawei) |
| R1-2212635 |
Draft CR on UL DAI applying to G-CS-RNTI DAI counting |
Moderator (Huawei) |
| R1-2212636 |
Draft CR on multicast HARQ-ACK |
Moderator (Huawei) |
| R1-2212637 |
Draft CR on Type-3 HARQ-ACK codebook for NACK-only mode for MBS |
Moderator (Huawei) |
| R1-2212638 |
Draft CR on DAI update for multicast DCI formats and Type-2 HARQ-ACK codebook |
Moderator (Huawei), Lenovo |
| R1-2212639 |
Draft CR on the cancellation procedure for the support of HARQ-ACK feedback for multicast |
Moderator (Huawei) |
| R1-2212640 |
Draft CR on DCI for enabling/disabling HARQ-ACK for MBS |
Moderator (Huawei) |
| R1-2212707 |
Draft CR on broadcast search space monitoring occasion determination |
Moderator (CMCC) |
| R1-2212708 |
Draft CR on terms of G-RNTI and MTCH in TS38.212 |
Moderator (CMCC), ZTE |
| R1-2212709 |
Draft CR on terms of G-RNTI and MTCH in TS38.213 |
Moderator (CMCC), ZTE |
| R1-2212710 |
Draft CR on terms of G-RNTI and MTCH in TS38.214 |
Moderator (CMCC), ZTE |
| R1-2212711 |
Draft CR on MCCH change notification |
Moderator (CMCC) |
| R1-2212712 |
Draft editorial CR on G-CS-RNTI |
Moderator (CMCC), vivo |
| R1-2212761 |
Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2212762 |
Moderator’s summary#3 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2212772 |
Draft CR on format 4_0 DCI size alignment in SCell |
Moderator (CMCC), CATT |
| R1-2212776 |
Draft CR on interpretation of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, Qualcomm, Samsung, vivo |
| R1-2212777 |
Draft CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated |
| R1-2212778 |
Draft CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated |
| R1-2212805 |
CR on interpretation of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, Qualcomm, Samsung, vivo, ZTE |
| R1-2212806 |
CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated |
| R1-2212807 |
CR on alignment of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, vivo, ZTE, Qualcomm |
| R1-2212829 |
CR on DAI counting for ‘dci-enabler’ in DCI indicating value 0 |
Moderator (Huawei), Langbo, Lenovo |
| R1-2212841 |
Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) |
Ad-Hoc Chair (Huawei) |
| R1-2212921 |
Draft CR on format 4_0 DCI size alignment in SCell |
Moderator (CMCC), CATT, ZTE |
| R1-2212922 |
CR on broadcast search space monitoring occasion determination |
Moderator (CMCC) |
| R1-2212942 |
Draft CR on HARQ-ACK codebook generation for RRC disabled HARQ-ACK feedback |
Moderator (Huawei), Lenovo, Samsung, MediaTek, Qualcomm |
| R1-2212943 |
Draft CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated |
| R1-2212944 |
CR on interpretation of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, Qualcomm, Samsung, vivo, ZTE |
| R1-2212945 |
CR on handling SR and NACK-only collision |
Moderator (Huawei), vivo |
| R1-2212970 |
CR on PUCCH resource determination of multicast HARQ-ACK |
Moderator (Huawei), HiSilicon, CBN, Nokia, Nokia Shanghai Bell, ZTE, Samsung |
| R1-2212971 |
CR on multiplexing HARQ-ACK for DG and SPS multicast and unicast |
Moderator (Huawei), HiSilicon, CBN, vivo, Samsung, Qualcomm |
| R1-2212972 |
CR on HARQ-ACK codebook generation for RRC disabled HARQ-ACK feedback |
Moderator (Huawei), Lenovo, Samsung, MediaTek, Qualcomm |
| R1-2212973 |
CR on NACK-only mode 2 multicast feedback |
Moderator (Huawei), Qualcomm Incorporated, Samsung |
| R1-2212974 |
CR on interpretation of moreThanOneNackOnlyMode |
Moderator (Huawei), HiSilicon, CBN, Qualcomm, vivo, ZTE |
| R1-2212975 |
CR on DAI counting for ‘dci-enabler’ in DCI indicating value 0 |
Moderator (Huawei), Langbo, Lenovo |
| R1-2212985 |
CR on format 4_0 DCI size alignment in SCell |
Moderator (CMCC), CATT, ZTE, MediaTek |
| R1-2212986 |
CR on rate-matching pattern for MBS broadcast reception |
Moderator (CMCC), MediaTek |
| R1-2212987 |
Moderator’s summary#4 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| 8.13 |
Maintenance on NR Dynamic spectrum sharing (DSS) |
|
| R1-2211492 |
Remaining issue in Rel-17 SCell-to-PCell scheduling |
OPPO |
| R1-2212096 |
Clarification for cross-carrier scheduling from SCell to P(S)Cell |
Qualcomm Incorporated |
| R1-2212162 |
Clarifications for Cross-carrier scheduling from SCell to P(S)Cell |
Ericsson |
| R1-2212784 |
Summary#1 of Rel17 Maintenance on NR Dynamic spectrum sharing (DSS) |
Moderator (Ericsson) |
| R1-2212842 |
Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) |
Ad-hoc Chair (CMCC) |
| 8.14 |
Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network |
|
| R1-2210871 |
Discussion on NTN SIB accumulation for IoT NTN |
Huawei, HiSilicon |
| R1-2211457 |
Draft CR on correction for UE performing pre-compensation |
OPPO |
| R1-2211766 |
On SIB accumulation in IoT NTN |
Ericsson Limited |
| R1-2212097 |
Maintenance on NB-IoT/eMTC support for NTN |
Qualcomm Incorporated |
| R1-2212293 |
Draft CR on correction of IoT NTN with segment gap in 36.211 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2212294 |
Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network |
Nokia, Nokia Shanghai Bell |
| R1-2212451 |
Support of SIB accumulation in IoT-NTN |
Sony |
| R1-2212548 |
Summary of [111-R17-IoT_NTN] Email discussion |
Moderator (MediaTek) |
| R1-2212553 |
Summary of [111-R17-IoT_NTN] Email discussion |
Moderator (MediaTek) |
| R1-2212843 |
Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) |
Ad-Hoc Chair (Huawei) |
| R1-2212931 |
Summary#2 of [111-R17-IoT_NTN] Email discussion |
Moderator (MediaTek) |
| 8.16 |
Rel-17 UE features |
|
| R1-2212895 |
Updated RAN1 UE features list for Rel-17 NR after RAN1 #111 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2212896 |
Draft LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#111 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2212897 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#111 |
RAN1, AT&T, NTT DOCOMO |
| 8.16.1 |
UE features topics 1 |
|
| R1-2210986 |
Remaining issues on Rel-17 UE features (MBS) |
vivo |
| R1-2211041 |
Discussion on UE features for topics 1 |
ZTE |
| R1-2211069 |
Remaining issues for UE features topics 1 |
Nokia, Nokia Shanghai Bell |
| R1-2211893 |
Rel-17 UE features topics set #1 |
Ericsson |
| R1-2211968 |
Discussion on remaining issues regarding Rel-17 RAN1 UE features topics 1 |
NTT DOCOMO, INC. |
| R1-2212098 |
Discussion on Rel-17 UE features topic 1 |
Qualcomm Incorporated |
| R1-2212268 |
Views on UE feature Topic 1 |
MediaTek Inc. |
| R1-2212472 |
Remaining issues for UE features topics 1 |
Huawei, HiSilicon |
| R1-2212525 |
Summary#1 on UE features for NR coverage enhancement |
Moderator (NTT DOCOMO, INC.) |
| R1-2212526 |
Summary#1 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2212527 |
Summary#1 on UE features for RedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2212529 |
Session Notes for R17 UE Features 1 |
Moderator (NTT DOCOMO, INC.) |
| R1-2212756 |
Summary#2 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2212891 |
Summary#2 on UE features for NR coverage enhancement |
Moderator (NTT DOCOMO, INC.) |
| R1-2212892 |
Summary#3 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2212893 |
Summary#2 on UE features for RedCap |
Moderator (NTT DOCOMO, INC.) |
| 8.16.2 |
UE features topics 2 |
|
| R1-2211796 |
View on Rel-17 UE features |
Apple |
| R1-2211936 |
Summary of UE features topics 2 |
Moderator (AT&T) |
| R1-2211937 |
Session Notes of AI 8.16.2 (NR_FeMIMO, NR_ext_to_71GHz, NR_NTN_solutions, IoT over NTN, NR_IAB_enh, NR_DSS, LTE_NR_DC_enh2, NR_pos_enh, and NR_DL1024QAM_FR1) |
Ad-Hoc Chair (AT&T) |
| R1-2212163 |
UE features topics 2 |
Ericsson |
| R1-2212493 |
Remaining issues for UE features topics 2 |
Huawei, HiSilicon |
| 8.17 |
Other |
|
| R1-2210987 |
Remaining issues of NR SDT in RRC INACTIVE state |
vivo |
| R1-2210988 |
Correction of CG PUSCH repetition in SDT |
vivo |
| R1-2210989 |
Correction of redundancy version of CG PUSCH repetitions in SDT |
vivo |
| R1-2211276 |
Correction on repetition for CG-SDT in TS 38.213 |
ZTE, Sanechips |
| R1-2211277 |
Discussion on repetition and redundancy version for CG-SDT |
ZTE, Sanechips |
| R1-2211380 |
Discussion on redundancy version for PUSCH repetitions during SDT |
Intel Corporation |
| R1-2211381 |
Correction on CG-PUSCH repetitions for CG-SDT operation |
Intel Corporation |
| R1-2212024 |
Discussion on the repetition aspect for SDT in active state |
Samsung |
| R1-2212025 |
Draft CR for the repetition aspect for SDT in active state |
Samsung |
| R1-2212492 |
Remaining issues on repetition for CG-SDT |
Huawei, HiSilicon |
| R1-2212751 |
Summary #1 on remaining issues of SDT |
Moderator (ZTE) |
| R1-2212844 |
Session notes for 8.17 (Other) |
Ad-hoc Chair (CMCC) |
| R1-2212932 |
Summary #2 on remaining issues of SDT |
Moderator (ZTE) |
| 9.1.1.1 |
Unified TCI framework extension for multi-TRP |
|
| R1-2210845 |
Unified TCI framework extension for multi-TRP |
FUTUREWEI |
| R1-2210911 |
Discussion on unified TCI framework extension for multi-TRP |
Huawei, HiSilicon |
| R1-2210925 |
Further Discussion on Unified TCI Extension for MTRP |
InterDigital, Inc. |
| R1-2210935 |
Enhancements on unified TCI framework extension for multi-TRP |
ZTE |
| R1-2210990 |
Discussion on unified TCI framework extension for multi-TRP |
vivo |
| R1-2211051 |
Unified TCI framework extension for multi-TRP |
Ericsson |
| R1-2211070 |
Views on unified TCI extension for MTRP |
Fujitsu |
| R1-2211114 |
Discussion on unified TCI framework extension for M-TRP operation |
Hyundai Motor Company |
| R1-2211167 |
Discussion on unified TCI framework extension for multi-TRP operation |
CATT |
| R1-2211217 |
Unified TCI framework extension for multi-TRP |
PANASONIC |
| R1-2211219 |
Discussion on unified TCI framework extension for multi-TRP |
Spreadtrum Communications |
| R1-2211290 |
Discussion of unified TCI framework for multi-TRP |
Lenovo |
| R1-2211334 |
Unified TCI framework extension for multi-TRP |
xiaomi |
| R1-2211382 |
Unified TCI Framework for Multi-TRP |
Intel Corporation |
| R1-2211425 |
Unified TCI framework extension for multi-TRP |
OPPO |
| R1-2211512 |
Discussion on unified TCI framework extension for multi-TRP |
Transsion Holdings |
| R1-2211588 |
Multi-TRP enhancements for the unified TCI framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2211664 |
Discussion on unified TCI framework extension for multi-TRP |
CMCC |
| R1-2211797 |
Extension of unified TCI framework for multi-TRP |
Apple |
| R1-2211859 |
Unified TCI framework extension for multi-TRP/panel |
LG Electronics |
| R1-2211880 |
Discussion on unified TCI framework extension for multi-TRP |
FGI |
| R1-2211886 |
Unified TCI framework extension for multi-TRP |
Sharp |
| R1-2211969 |
Discussion on unified TCI framework extension for multi-TRP |
NTT DOCOMO, INC. |
| R1-2212026 |
Views on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2212099 |
Extension of unified TCI framework for mTRP |
Qualcomm Incorporated |
| R1-2212167 |
Unified TCI framework extension for multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2212211 |
Discussion on unified TCI framework extension for multi-TRP |
Google |
| R1-2212236 |
Unified TCI framework extension for multi-TRP |
MediaTek Inc. |
| R1-2212333 |
Discussion on unified TCI framework extension for multi-TRP |
ITRI |
| R1-2212352 |
Discussion on unified TCI framework extension for multi-TRP |
NEC |
| R1-2212376 |
Discussion on unified TCI framework extension for multi-TRP operation |
TCL Communication Ltd. |
| R1-2212420 |
Discussion on Unified TCI framework extension for multi-TRP |
CEWiT |
| R1-2212522 |
Moderator summary on extension of unified TCI framework (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2212759 |
Moderator summary on extension of unified TCI framework (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2212878 |
Moderator summary on extension of unified TCI framework (Round 2) |
Moderator (MediaTek Inc.) |
| 9.1.1.2 |
Two TAs for multi-DCI |
|
| R1-2210846 |
Enhancements to support two TAs for multi-DCI |
FUTUREWEI |
| R1-2210912 |
Study on TA enhancement for UL M-TRP transmssion |
Huawei, HiSilicon |
| R1-2210926 |
Enhanced Operation of mTRP with Multiple TA |
InterDigital, Inc. |
| R1-2210936 |
TA enhancement for multi-DCI |
ZTE |
| R1-2210991 |
Discussion on two TAs for multi-DCI-based multi-TRP operation |
vivo |
| R1-2211052 |
Two TAs for multi-DCI |
Ericsson |
| R1-2211168 |
Discussion on Two TAs for UL multi-TRP operation |
CATT |
| R1-2211220 |
Discussion on two TAs for multi-DCI based multi-TRP |
Spreadtrum Communications |
| R1-2211291 |
Discussion of two TAs for multi-DCI UL transmission |
Lenovo |
| R1-2211335 |
Discussion on two TAs for multi-TRP operation |
xiaomi |
| R1-2211383 |
On two TAs for multi-DCI |
Intel Corporation |
| R1-2211426 |
Two TAs for multi-DCI |
OPPO |
| R1-2211513 |
Discussion on two TAs for multi-DCI based multi-TRP operation |
Transsion Holdings |
| R1-2211576 |
Discussion on two TAs for multi-DCI based on multi-TRP operation |
TCL Communication Ltd. |
| R1-2211665 |
Discussion on two TAs for multi-DCI |
CMCC |
| R1-2211798 |
Two TAs for multi-DCI based Uplink Transmissions |
Apple |
| R1-2211860 |
Two TAs for multi-TRP/panel |
LG Electronics |
| R1-2211970 |
Discussion on two TAs for multi-DCI |
NTT DOCOMO, INC. |
| R1-2212027 |
Views on two TAs for m-DCI |
Samsung |
| R1-2212100 |
Supporting two TAs for multi-DCI based mTRP |
Qualcomm Incorporated |
| R1-2212168 |
Two TAs for UL multi-DCI multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2212187 |
Two TAs for multi-DCI |
Sharp |
| R1-2212212 |
Discussion on two TAs for multi-DCI |
Google |
| R1-2212237 |
UL Tx Timing Management for MTRP Operation |
MediaTek Inc. |
| R1-2212353 |
Discussion on two TAs for multi-DCI |
NEC |
| R1-2212589 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2212775 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2212862 |
Moderator Summary #3 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2212957 |
[Draft] LS on Multi-DCI Multi-TRP with two TAs |
Ericsson |
| R1-2213004 |
LS on Multi-DCI Multi-TRP with two TAs |
RAN1, Ericsson |
| 9.1.2 |
CSI enhancement |
|
| R1-2210913 |
CSI enhancement for coherent JT and mobility |
Huawei, HiSilicon |
| R1-2210927 |
Discussion on CSI Enhancements for CJT and Medium/High UE Velocities |
InterDigital, Inc. |
| R1-2210937 |
CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2210992 |
Discussion on CSI enhancement for high-medium UE velocities and coherent JT |
vivo |
| R1-2211118 |
On CSI Enhancement |
Google |
| R1-2211169 |
CSI enhancement for high/medium UE velocities and coherent JT |
CATT |
| R1-2211221 |
Discussion on CSI enhancement for high/medium UE velocities and coherent JT |
Spreadtrum Communications |
| R1-2211292 |
Discussion of CSI enhancement for high speed UE and coherent JT |
Lenovo |
| R1-2211336 |
Views on CSI enhancement for high/medium UE velocities and CJT |
xiaomi |
| R1-2211384 |
On CSI enhancements |
Intel Corporation |
| R1-2211427 |
CSI enhancement for high/medium UE velocities and coherent JT |
OPPO |
| R1-2211587 |
CSI enhancements for medium UE velocities and coherent JT |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2211603 |
Further considerations on CSI enhancement for high/medium UE velocities and CJT |
Sony |
| R1-2211666 |
Discussion on CSI enhancement for high/medium UE velocities and CJT |
CMCC |
| R1-2211799 |
Views on Rel-18 MIMO CSI enhancement |
Apple |
| R1-2211861 |
Potential CSI enhancement for high/medium UE velocities and coherent JT |
LG Electronics |
| R1-2211887 |
CSI enhancement |
Sharp |
| R1-2211939 |
Views on CSI Enhancements for CJT |
AT&T |
| R1-2211971 |
Discussion on CSI enhancement |
NTT DOCOMO, INC. |
| R1-2212028 |
Moderator summary on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2212029 |
Summary of OFFLINE discussion on Rel-18 MIMO CSI |
Moderator (Samsung) |
| R1-2212030 |
Views on CSI enhancements |
Samsung |
| R1-2212101 |
CSI enhancements for medium UE velocities and Coherent-JT |
Qualcomm Incorporated |
| R1-2212169 |
CSI enhancement for high/medium UE velocities and CJT |
Nokia, Nokia Shanghai Bell |
| R1-2212174 |
On CSI enhancements for Rel-18 NR MIMO evolution |
Ericsson |
| R1-2212232 |
CSI Enhancements |
MediaTek Inc. |
| R1-2212276 |
Discussion on CSI enhancement |
Mavenir |
| R1-2212348 |
Discussion on CSI enhancement |
NEC |
| R1-2212421 |
Discussion on CSI Enhancements for high/medium UE velocities and coherent JT |
CEWiT |
| R1-2212697 |
On CSI enhancements for Rel-18 NR MIMO evolution |
Ericsson |
| R1-2212706 |
Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 |
Moderator (Samsung) |
| R1-2212721 |
Moderator Summary on Rel-18 CSI enhancements: Tuesday offline session |
Moderator (Samsung) |
| R1-2212819 |
Moderator Summary#3 on Rel-18 CSI enhancements: Round 2 |
Moderator (Samsung) |
| R1-2212870 |
Moderator Summary on Rel-18 CSI enhancements: Thursday offline session |
Moderator (Samsung) |
| 9.1.3.1 |
Increased number of orthogonal DMRS ports |
|
| R1-2210847 |
On increasing the number of orthogonal DM-RS ports for MU-MIMO |
FUTUREWEI |
| R1-2210914 |
Enhancements on DMRS in Rel-18 |
Huawei, HiSilicon |
| R1-2210928 |
Discussion on DMRS Enhancements |
InterDigital, Inc. |
| R1-2210934 |
Discussions on increased number of orthogonal DMRS ports |
New H3C Technologies Co., Ltd. |
| R1-2210938 |
DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO |
ZTE |
| R1-2210993 |
Discussion on DMRS enhancements |
vivo |
| R1-2211119 |
On DMRS Enhancement |
Google |
| R1-2211170 |
On DMRS enhancements in Rel-18 |
CATT |
| R1-2211222 |
Discussion on increased number of orthogonal DMRS ports |
Spreadtrum Communications |
| R1-2211293 |
Discussion of increased number of orthogonal DMRS ports |
Lenovo |
| R1-2211337 |
Discussion on DMRS enhancement |
xiaomi |
| R1-2211385 |
DMRS Enhancements for Rel-18 NR |
Intel Corporation |
| R1-2211428 |
DMRS enhancement for Rel-18 MIMO |
OPPO |
| R1-2211586 |
On increased number of orthogonal DMRS ports |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2211667 |
Discussion on increased number of orthogonal DMRS ports |
CMCC |
| R1-2211771 |
On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO |
Ericsson |
| R1-2211800 |
Views on supporting increased number of orthogonal DMRS ports |
Apple |
| R1-2211862 |
Increased number of orthogonal DMRS ports |
LG Electronics |
| R1-2211888 |
Increased number of orthogonal DMRS ports |
Sharp |
| R1-2211972 |
Discussion on DMRS enhancements |
NTT DOCOMO, INC. |
| R1-2212031 |
Views on DMRS enhancements |
Samsung |
| R1-2212102 |
Design for increased number of orthogonal DMRS ports |
Qualcomm Incorporated |
| R1-2212170 |
Rel-18 UL and DL DMRS Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2212233 |
Increased number of orthogonal DMRS ports |
MediaTek Inc. |
| R1-2212349 |
Discussion on increased number of orthogonal DMRS ports |
NEC |
| R1-2212523 |
FL summary#1 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2212524 |
FL summary#2 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2212760 |
FL summary#3 on DMRS |
Moderator (NTT DOCOMO) |
| 9.1.3.2 |
SRS enhancement targeting TDD CJT and 8 TX operation |
|
| R1-2210848 |
SRS enhancements for TDD CJT and 8TX operation |
FUTUREWEI |
| R1-2210915 |
SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 |
Huawei, HiSilicon |
| R1-2210929 |
Enhanced SRS for CJT and 8TX UEs |
InterDigital, Inc. |
| R1-2210939 |
SRS enhancement targeting TDD CJT and 8 TX operation |
ZTE |
| R1-2210994 |
Discussion on SRS enhancement |
vivo |
| R1-2211120 |
On SRS Enhancement |
Google |
| R1-2211171 |
On SRS enhancement in Rel-18 |
CATT |
| R1-2211223 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
Spreadtrum Communications |
| R1-2211272 |
Views on SRS enhancement targeting TDD CJT and 8 TX operation |
KDDI Corporation |
| R1-2211294 |
Discussion of SRS enhancement |
Lenovo |
| R1-2211338 |
Discussion on SRS enhancements |
xiaomi |
| R1-2211386 |
Discussion on SRS enhancement in Rel-18 |
Intel Corporation |
| R1-2211429 |
SRS enhancement targeting TDD CJT and 8 TX operation |
OPPO |
| R1-2211554 |
Discussion on SRS enhancement targeting TDD CJT |
ETRI |
| R1-2211604 |
Considerations on precoded SRS |
Sony |
| R1-2211668 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
CMCC |
| R1-2211801 |
Views on Rel-18 MIMO SRS enhancement |
Apple |
| R1-2211863 |
SRS enhancement targeting TDD CJT and 8 TX operation |
LG Electronics |
| R1-2211889 |
SRS enhancement targeting TDD CJT and 8 TX operation |
Sharp |
| R1-2211973 |
Discussion on SRS enhancement |
NTT DOCOMO, INC. |
| R1-2212032 |
Views on SRS enhancements |
Samsung |
| R1-2212103 |
SRS enhancement for TDD CJT and 8 Tx operation |
Qualcomm Incorporated |
| R1-2212171 |
SRS enhancement for TDD CJT and 8Tx operation |
Nokia, Nokia Shanghai Bell |
| R1-2212350 |
Discussion on SRS enhancement |
NEC |
| R1-2212377 |
On SRS enhancements targeting TDD CJT and 8 TX operation |
Ericsson |
| R1-2212694 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2212695 |
FL Summary #3 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2212696 |
FL Summary #4 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2212941 |
FL Summary #5 on SRS enhancements |
Moderator (FUTUREWEI) |
| 9.1.4.1 |
UL precoding indication for multi-panel transmission |
|
| R1-2210916 |
Discussion on UL precoding indication for multi-panel transmission |
Huawei, HiSilicon |
| R1-2210930 |
Uplink Precoding Indication and Multi-panel Transmission |
InterDigital, Inc. |
| R1-2210940 |
Enhancements on UL precoding indication for multi-panel transmission |
ZTE |
| R1-2210995 |
Discussion on UL precoding indication for multi-panel transmission |
vivo |
| R1-2211071 |
Discussion on UL precoding indication for multi-panel transmission |
Fujitsu |
| R1-2211121 |
On Simultaneous Multi-Panel Transmission |
Google |
| R1-2211172 |
Enhancements on UL precoding indication for multi-panel transmission |
CATT |
| R1-2211218 |
UL Precoding for Multi-panel Transmission |
PANASONIC |
| R1-2211224 |
Discussion on UL precoding indication for multi-panel transmission |
Spreadtrum Communications |
| R1-2211295 |
UL precoding indication for multi-panel transmission |
Lenovo |
| R1-2211339 |
Enhancements on multi-panel uplink transmission |
xiaomi |
| R1-2211387 |
UL precoding indication for multi-panel transmission |
Intel Corporation |
| R1-2211430 |
Transmission scheme and UL precoding indicaton for multi-panel transmission |
OPPO |
| R1-2211591 |
On UL precoding indication for simultaneous multi-panel transmission |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2211605 |
Considerations on 1 vs. 2 CWs for SDM multi-panel transmissions |
Sony |
| R1-2211669 |
Discussion on UL precoding indication for multi-panel transmission |
CMCC |
| R1-2211802 |
Views on UL precoding indication for multi-panel simultaneous PUSCH transmissions |
Apple |
| R1-2211864 |
UL precoding indication for multi-panel transmission |
LG Electronics |
| R1-2211890 |
Views on UL multi-panel transmission |
Sharp |
| R1-2211974 |
Discussion on multi-panel transmission |
NTT DOCOMO, INC. |
| R1-2212033 |
Views on UL precoding indication for STxMP |
Samsung |
| R1-2212104 |
Simultaneous multi-panel transmission |
Qualcomm Incorporated |
| R1-2212172 |
Precoder Indication for Multi-Panel UL Transmission |
Nokia, Nokia Shanghai Bell |
| R1-2212238 |
Simultaneous transmission across multiple UE panels |
MediaTek Inc. |
| R1-2212354 |
Discussion on UL precoding indication for multi-panel transmission |
NEC |
| R1-2212375 |
UL precoding indication for multi-panel transmission |
Ericsson |
| R1-2212579 |
Summary #1 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2212580 |
Summary #2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2212581 |
Summary #3 on Rel-18 STxMP |
Moderator (OPPO) |
| 9.1.4.2 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
|
| R1-2210917 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Huawei, HiSilicon |
| R1-2210931 |
Discussion on SRI/TPMI Enhancement for 8TX UE |
InterDigital, Inc. |
| R1-2210941 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
ZTE |
| R1-2210996 |
Discussion on enabling 8 TX UL transmission |
vivo |
| R1-2211122 |
On SRI/TPMI Indication for 8Tx Transmission |
Google |
| R1-2211173 |
Discussion on codebook and SRI/TPMI enhancement for UL 8 TX |
CATT |
| R1-2211225 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Spreadtrum Communications |
| R1-2211296 |
SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| R1-2211340 |
Enhancements on 8Tx uplink transmission |
xiaomi |
| R1-2211388 |
Discussion on enhancement for 8Tx UL transmission |
Intel Corporation |
| R1-2211431 |
SRI TPMI enhancement for 8 TX UL transmission |
OPPO |
| R1-2211670 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
CMCC |
| R1-2211803 |
Views on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Apple |
| R1-2211865 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
LG Electronics |
| R1-2211891 |
Views on 8 TX UL transmission |
Sharp |
| R1-2211894 |
SRI/TPMI Enhancement for Enabling 8 TX UL Transmission |
Ericsson |
| R1-2211975 |
Discussion on 8 TX UL transmission |
NTT DOCOMO, INC. |
| R1-2212034 |
Views on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2212105 |
Enhancements for 8 Tx UL transmissions |
Qualcomm Incorporated |
| R1-2212173 |
UL enhancements for enabling 8Tx UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2212234 |
SRI/TPMI enhancement for enabling 8 Tx UL transmission |
MediaTek Inc. |
| R1-2212351 |
Discussion on SRI/TPMI enhancement |
NEC |
| R1-2212422 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
CEWiT |
| R1-2212556 |
FL Summary on SRI/TPMI Enhancements; Preparatory |
Moderator (InterDigital) |
| R1-2212557 |
FL Summary on SRI/TPMI Enhancements; First Round |
Moderator (InterDigital) |
| R1-2212558 |
FL Summary on SRI/TPMI Enhancements; Second Round |
Moderator (InterDigital) |
| R1-2212559 |
FL Summary on SRI/TPMI Enhancements; Third Round |
Moderator (InterDigital) |
| R1-2212560 |
Recommended Direction on SRI/TPMI Enhancements for RAN1#112 |
Moderator (InterDigital) |
| R1-2212659 |
SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| 9.2 |
Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface |
|
| R1-2212106 |
Technical report for Rel-18 SI on AI and ML for NR air interface |
Qualcomm Incorporated |
| R1-2212845 |
Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) |
Ad-hoc Chair (CMCC) |
| 9.2.1 |
General aspects of AI/ML framework |
|
| R1-2210840 |
Continued discussion on common AI/ML characteristics and operations |
FUTUREWEI |
| R1-2210884 |
Discussion on general aspects of AI/ML framework |
Huawei, HiSilicon |
| R1-2210997 |
Discussions on AI/ML framework |
vivo |
| R1-2211056 |
Discussion on general aspects of common AI PHY framework |
ZTE |
| R1-2211072 |
Discussion on general aspects of AI/ML framework |
Fujitsu |
| R1-2211123 |
On General Aspects of AI/ML Framework |
Google |
| R1-2211188 |
General aspects of AI/ML framework |
CATT |
| R1-2211215 |
Discussion on general aspects of AI/ML framework |
KDDI Corporation |
| R1-2211226 |
Discussion on general aspects of AIML framework |
Spreadtrum Communications |
| R1-2211287 |
Discussion on general aspects of AI/ML framework |
Ericsson |
| R1-2211354 |
Views on the general aspects of AI/ML framework |
xiaomi |
| R1-2211392 |
Discussion on general aspects of AI/ML framework |
Intel Corporation |
| R1-2211477 |
On general aspects of AI/ML framework |
OPPO |
| R1-2211508 |
Discussions on Common Aspects of AI/ML Framework |
TCL Communication |
| R1-2211555 |
Discussion on general aspects of AI/ML framework for NR air interface |
ETRI |
| R1-2211606 |
Considerations on common AI/ML framework |
Sony |
| R1-2211671 |
Discussion on general aspects of AI/ML framework |
CMCC |
| R1-2211714 |
General aspects of AI and ML framework for NR air interface |
NVIDIA |
| R1-2211729 |
Discussion on general aspects of AI/ML framework |
InterDigital, Inc. |
| R1-2211772 |
General aspects of AI/ML framework |
Lenovo |
| R1-2211804 |
Discussion on general aspect of AI/ML framework |
Apple |
| R1-2211866 |
General aspects on AI/ML framework |
LG Electronics |
| R1-2211910 |
Considerations on general aspects on AI-ML framework |
CAICT |
| R1-2211933 |
Discussion on general aspects of AI/ML framework |
Panasonic |
| R1-2211934 |
General aspects of AI/ML framework |
AT&T |
| R1-2211976 |
Discussion on general aspects of AI/ML framework |
NTT DOCOMO, INC. |
| R1-2212035 |
General aspects of AI ML framework and evaluation methodology |
Samsung |
| R1-2212107 |
General aspects of AI/ML framework |
Qualcomm Incorporated |
| R1-2212225 |
General aspects of AI/ML framework |
MediaTek Inc. |
| R1-2212312 |
Discussion on AI/ML Model Life Cycle Management |
Rakuten Mobile, Inc |
| R1-2212326 |
Further discussion on the general aspects of ML for Air-interface |
Nokia, Nokia Shanghai Bell |
| R1-2212355 |
Discussion on general aspects of AI ML framework |
NEC |
| R1-2212654 |
Summary#1 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2212655 |
Summary#2 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2212656 |
Summary#3 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2212657 |
Summary#4 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2212658 |
Final summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2213003 |
Final summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| 9.2.2.1 |
Evaluation on AI/ML for CSI feedback enhancement |
|
| R1-2210841 |
Continued discussion on evaluation of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2210885 |
Evaluation on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2210954 |
Evaluation of AI-CSI |
Ericsson |
| R1-2210998 |
Evaluation on AI/ML for CSI feedback enhancement |
vivo |
| R1-2211057 |
Evaluation on AI for CSI feedback enhancement |
ZTE |
| R1-2211073 |
Evaluation on AI/ML for CSI feedback enhancement |
Fujitsu |
| R1-2211124 |
On Evaluation of AI/ML based CSI |
Google |
| R1-2211189 |
Evaluation methodology and results on AI/ML for CSI feedback enhancement |
CATT |
| R1-2211227 |
Discussion on evaluation on AIML for CSI feedback enhancement |
Spreadtrum Communications, BUPT |
| R1-2211258 |
Evaluation on AI/ML for CSI feedback enhancement |
Comba |
| R1-2211355 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
xiaomi |
| R1-2211393 |
Evaluation for CSI feedback enhancements |
Intel Corporation |
| R1-2211478 |
Evaluation methodology and preliminary results on AI/ML for CSI feedback enhancement |
OPPO |
| R1-2211525 |
Evaluation on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2211556 |
Evaluation on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2211589 |
Evaluation of AI/ML based methods for CSI feedback enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2211672 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2211716 |
Evaluation of AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2211731 |
Evaluation on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2211773 |
Evaluation on AI/ML for CSI feedback |
Lenovo |
| R1-2211805 |
Evaluation for AI/ML based CSI feedback enhancement |
Apple |
| R1-2211867 |
Evaluation on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2211892 |
Model Quantization for CSI feedback |
Sharp |
| R1-2211911 |
Some discussions on evaluation on AI-ML for CSI feedback |
CAICT |
| R1-2211977 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2212036 |
Evaluation on AI ML for CSI feedback enhancement |
Samsung |
| R1-2212108 |
Evaluation on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2212226 |
Evaluation on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2212327 |
Evaluation of ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2212452 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2212669 |
Summary#1 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| R1-2212670 |
Summary#2 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| R1-2212671 |
Summary#3 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| R1-2212672 |
Summary#4 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| R1-2212673 |
Summary#5 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| R1-2212966 |
Summary#6 for CSI evaluation of [111-R18-AI/ML] |
Moderator (Huawei) |
| 9.2.2.2 |
Other aspects on AI/ML for CSI feedback enhancement |
|
| R1-2210842 |
Continued discussion on other aspects of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2210886 |
Discussion on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2210955 |
Discussion on AI-CSI |
Ericsson |
| R1-2210999 |
Other aspects on AI/ML for CSI feedback enhancement |
vivo |
| R1-2211058 |
Discussion on other aspects for AI CSI feedback enhancement |
ZTE |
| R1-2211074 |
Views on specification impact for CSI compression with two-sided model |
Fujitsu |
| R1-2211125 |
On Enhancement of AI/ML based CSI |
Google |
| R1-2211133 |
Discussion on AI/ML for CSI feedback enhancement |
Panasonic |
| R1-2211190 |
Other aspects on AI/ML for CSI feedback enhancement |
CATT |
| R1-2211228 |
Discussion on other aspects on AIML for CSI feedback |
Spreadtrum Communications |
| R1-2211356 |
Views on potential specification impact for CSI feedback based on AI/ML |
xiaomi |
| R1-2211394 |
Use-cases and specification for CSI feedback |
Intel Corporation |
| R1-2211479 |
On sub use cases and other aspects of AI/ML for CSI feedback enhancement |
OPPO |
| R1-2211509 |
Discussions on Sub-Use Cases in AI/ML for CSI Feedback Enhancement |
TCL Communication |
| R1-2211526 |
Discussion on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2211557 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2211607 |
Considerations on CSI measurement enhancements via AI/ML |
Sony |
| R1-2211673 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2211718 |
AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2211733 |
Discussion on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2211750 |
Discussion on AI/ML for CSI feedback enhancement |
NEC |
| R1-2211774 |
Further aspects of AI/ML for CSI feedback |
Lenovo |
| R1-2211806 |
Discussion on other aspects of AI/ML for CSI enhancement |
Apple |
| R1-2211868 |
Other aspects on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2211912 |
Discussions on AI-ML for CSI feedback |
CAICT |
| R1-2211978 |
Discussion on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2212037 |
Representative sub use cases for CSI feedback enhancement |
Samsung |
| R1-2212109 |
Other aspects on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2212227 |
Other aspects on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2212328 |
Other aspects on ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2212453 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2212542 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2212641 |
Summary #1 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2212642 |
Summary #2 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2212643 |
Summary #3 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2212644 |
Summary #4 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2212909 |
Summary #5 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| 9.2.3.1 |
Evaluation on AI/ML for beam management |
|
| R1-2210843 |
Continued discussion on evaluation of AI/ML for beam management |
FUTUREWEI |
| R1-2210887 |
Evaluation on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2211000 |
Evaluation on AI/ML for beam management |
vivo |
| R1-2211059 |
Evaluation on AI for beam management |
ZTE |
| R1-2211075 |
Evaluation on AI/ML for beam management |
Fujitsu |
| R1-2211126 |
On Evaluation of AI/ML based Beam Management |
Google |
| R1-2211191 |
Evaluation methodology and results on AI/ML for beam management |
CATT |
| R1-2211229 |
Evaluation on AI for beam management |
Spreadtrum Communications |
| R1-2211288 |
Evaluation of AIML for beam management |
Ericsson |
| R1-2211315 |
Discussion for evaluation on AI/ML for beam management |
InterDigital, Inc. |
| R1-2211357 |
Evaluation on AI/ML for beam management |
xiaomi |
| R1-2211395 |
Evaluations for AI/ML beam management |
Intel Corporation |
| R1-2211480 |
Evaluation methodology and preliminary results on AI/ML for beam management |
OPPO |
| R1-2211527 |
Evaluation on AI/ML for beam management |
China Telecom |
| R1-2211674 |
Discussion on evaluation on AI/ML for beam management |
CMCC |
| R1-2211719 |
Evaluation of AI and ML for beam management |
NVIDIA |
| R1-2211775 |
Evaluation on AI/ML for beam management |
Lenovo |
| R1-2211807 |
Evaluation on AI/ML for beam management |
Apple |
| R1-2211869 |
Evaluation on AI/ML for beam management |
LG Electronics |
| R1-2211913 |
Some discussions on evaluation on AI-ML for Beam management |
CAICT |
| R1-2211979 |
Discussion on evaluation on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2212038 |
Evaluation on AI ML for Beam management |
Samsung |
| R1-2212110 |
Evaluation on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2212228 |
Evaluation on AI/ML for beam management |
MediaTek Inc. |
| R1-2212329 |
Evaluation of ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2212423 |
Evaluation on AI/ML for beam management |
CEWiT |
| R1-2212591 |
Feature lead summary #0 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2212592 |
Feature lead summary #1 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2212593 |
Feature lead summary #2 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2212594 |
Feature lead summary #3 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2212904 |
Feature lead summary #4 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2212905 |
Feature lead summary #5 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| 9.2.3.2 |
Other aspects on AI/ML for beam management |
|
| R1-2210844 |
Continued discussion on other aspects of AI/ML for beam management |
FUTUREWEI |
| R1-2210888 |
Discussion on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2211001 |
Other aspects on AI/ML for beam management |
vivo |
| R1-2211038 |
Discussion on other aspects of AI/ML beam management |
New H3C Technologies Co., Ltd. |
| R1-2211060 |
Discussion on other aspects for AI beam management |
ZTE |
| R1-2211076 |
Sub use cases and specification impact on AI/ML for beam management |
Fujitsu |
| R1-2211127 |
On Enhancement of AI/ML based Beam Management |
Google |
| R1-2211192 |
Other aspects on AI/ML for beam management |
CATT |
| R1-2211230 |
Discussion on other aspects on AIML for beam management |
Spreadtrum Communications |
| R1-2211289 |
Discussion on AI/ML for beam management |
Ericsson |
| R1-2211316 |
Discussion for other aspects on AI/ML for beam management |
InterDigital, Inc. |
| R1-2211358 |
Potential specification impact on AI/ML for beam management |
xiaomi |
| R1-2211396 |
Use-cases and Specification Impact for AI/ML beam management |
Intel Corporation |
| R1-2211481 |
Other aspects of AI/ML for beam management |
OPPO |
| R1-2211510 |
Discussions on Sub-Use Cases in AI/ML for Beam Management |
TCL Communication |
| R1-2211528 |
Other aspects on AI/ML for beam management |
China Telecom |
| R1-2211558 |
Discussion on other aspects on AI/ML for beam management |
ETRI |
| R1-2211590 |
Discussion on sub use cases of AI/ML beam management |
Panasonic |
| R1-2211608 |
Consideration on AI/ML for beam management |
Sony |
| R1-2211675 |
Discussion on other aspects on AI/ML for beam management |
CMCC |
| R1-2211721 |
AI and ML for beam management |
NVIDIA |
| R1-2211776 |
Further aspects of AI/ML for beam management |
Lenovo |
| R1-2211808 |
Discussion on other aspects of AI/ML for beam management |
Apple |
| R1-2211870 |
Other aspects on AI/ML for beam management |
LG Electronics |
| R1-2211914 |
Discussions on AI-ML for Beam management |
CAICT |
| R1-2211980 |
Discussion on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2212039 |
Representative sub use cases for beam management |
Samsung |
| R1-2212111 |
Other aspects on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2212150 |
Discussion on other aspects on AI/ML for beam management |
KT Corp. |
| R1-2212229 |
Other aspects on AI/ML for beam management |
MediaTek Inc. |
| R1-2212292 |
Continued Discussion on Performance Related Aspects of Codebook Enhancement with AI/ML |
Charter Communications, Inc |
| R1-2212320 |
Other aspects on AI/ML for beam management |
Rakuten Symphony |
| R1-2212330 |
Other aspects on ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2212372 |
Discussion on AI/ML for beam management |
NEC |
| R1-2212718 |
Summary#1 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2212719 |
Summary#2 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2212720 |
Summary#3 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2212927 |
Summary#4 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| 9.2.4.1 |
Evaluation on AI/ML for positioning accuracy enhancement |
|
| R1-2210854 |
Evaluation of AI/ML for Positioning Accuracy Enhancement |
Ericsson |
| R1-2210889 |
Evaluation on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2211002 |
Evaluation on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2211061 |
Evaluation on AI for positioning enhancement |
ZTE |
| R1-2211077 |
Further evaluation results and discussions of AI positioning accuracy enhancement |
Fujitsu |
| R1-2211128 |
On Evaluation of AI/ML based Positioning |
Google |
| R1-2211193 |
Evaluation methodology and results on AI/ML for positioning enhancement |
CATT |
| R1-2211359 |
Evaluation on AI/ML for positioning accuracy enhancement |
xiaomi |
| R1-2211482 |
Evaluation methodology and preliminary results on AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2211529 |
Evaluation on AI/ML for positioning accuracy enhancement |
China Telecom |
| R1-2211676 |
Discussion on evaluation on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2211715 |
Evaluation on AI/ML for positioning accuracy enhancement |
InterDigital, Inc. |
| R1-2211722 |
Evaluation of AI and ML for positioning enhancement |
NVIDIA |
| R1-2211777 |
Discussion on AI/ML Positioning Evaluations |
Lenovo |
| R1-2211809 |
On Evaluation on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2211871 |
Evaluation on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2211915 |
Some discussions on evaluation on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2212040 |
Evaluation on AI ML for Positioning |
Samsung |
| R1-2212112 |
Evaluation on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2212230 |
Evaluation on AI/ML for positioning accuracy enhancement |
MediaTek Inc. |
| R1-2212331 |
Evaluation of ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2212382 |
Evaluation on AI/ML for positioning accuracy enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212610 |
Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2212611 |
Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2212612 |
Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2212816 |
Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2212817 |
Final summary of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| 9.2.4.2 |
Other aspects on AI/ML for positioning accuracy enhancement |
|
| R1-2210855 |
Other Aspects of AI/ML Based Positioning Enhancement |
Ericsson |
| R1-2210890 |
Discussion on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2211003 |
Other aspects on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2211062 |
Discussion on other aspects for AI positioning enhancement |
ZTE |
| R1-2211078 |
Discussions on spec impacts of model training, data collection, model identification and model monitoring for AIML for positioning accuracy enhancement |
Fujitsu |
| R1-2211129 |
On Enhancement of AI/ML based Positioning |
Google |
| R1-2211194 |
Other aspects on AI/ML for positioning enhancement |
CATT |
| R1-2211231 |
Discussion on other aspects on AIML for positioning accuracy enhancement |
Spreadtrum Communications |
| R1-2211360 |
Views on the other aspects of AI/ML-based positioning accuracy enhancement |
xiaomi |
| R1-2211483 |
On sub use cases and other aspects of AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2211609 |
On AI/ML for positioning accuracy enhancement |
Sony |
| R1-2211677 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2211717 |
Designs and potential specification impacts of AIML for positioning |
InterDigital, Inc. |
| R1-2211725 |
AI and ML for positioning enhancement |
NVIDIA |
| R1-2211778 |
AI/ML Positioning use cases and Associated Impacts |
Lenovo |
| R1-2211810 |
On Other aspects on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2211872 |
Other aspects on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2211916 |
Discussions on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2211981 |
Discussion on AI/ML for positioning accuracy enhancement |
NTT DOCOMO, INC. |
| R1-2212041 |
Representative sub use cases for Positioning |
Samsung |
| R1-2212113 |
Other aspects on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2212214 |
Other aspects on AI-ML for positioning accuracy enhancement |
Baicells |
| R1-2212231 |
Other aspects on AI/ML for positioning accuracy enhancement |
MediaTek Inc. |
| R1-2212332 |
Other aspects on ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2212358 |
Discussion on AI/ML for positioning accuracy enhancement |
NEC |
| R1-2212383 |
On potential AI/ML solutions for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212549 |
FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2212742 |
FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2212783 |
FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2212877 |
FL summary #4 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| 9.3 |
Study on evolution of NR duplex operation |
|
| R1-2212374 |
TR 38.858 v0.1.0 for study on evolution of NR duplex operation |
Rapporteur (CMCC) |
| 9.3.1 |
Evaluation on NR duplex evolution |
|
| R1-2210876 |
Discussion on evaluation and methodologies on evolution of NR duplex operation |
Huawei, HiSilicon |
| R1-2210933 |
Discussion for Evaluation on NR duplex evolution |
New H3C Technologies Co., Ltd. |
| R1-2211004 |
Evaluation on NR duplex evolution |
vivo |
| R1-2211042 |
Discussion of evaluation on NR duplex evolution |
ZTE |
| R1-2211195 |
Discussion on evaluation on NR duplex evolution |
CATT |
| R1-2211232 |
Discussion on evaluation on NR duplex evolution |
Spreadtrum Communications, BUPT |
| R1-2211361 |
Discussion on evaluation on NR duplex evolution |
xiaomi |
| R1-2211397 |
Evaluation of NR Duplex Evolution |
Intel Corporation |
| R1-2211484 |
Discussion on evaluation on NR duplex evolution |
OPPO |
| R1-2211678 |
Summary#1 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2211679 |
Discussion on evaluation on NR duplex evolution |
CMCC |
| R1-2211708 |
Discussion on evaluation on NR duplex operation |
KT Corp. |
| R1-2211736 |
Discussion on evaluation for NR-duplex |
InterDigital, Inc. |
| R1-2211749 |
Evaluation of NR SBFD operation |
NEC |
| R1-2211783 |
Evaluation methodology for NR duplex evolution |
Kumu Networks |
| R1-2211811 |
On evaluations for NR duplex evolution |
Apple |
| R1-2211921 |
Study on Evaluation for NR duplex evolution |
LG Electronics |
| R1-2211941 |
Evaluation of NR duplex evolution |
Ericsson |
| R1-2211982 |
Discussion on evaluation on NR duplex evolution |
NTT DOCOMO, INC. |
| R1-2212042 |
Discussion on evaluation for NR duplex evolution |
Samsung |
| R1-2212114 |
On Deployment scenarios and evaluation Methodology for NR duplex evolution |
Qualcomm Incorporated |
| R1-2212248 |
Deployment scenarios and evaluation methodology for NR duplex evolution |
MediaTek Inc. |
| R1-2212283 |
On the evaluation methodology for NR duplexing enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2212450 |
Evaluation of NR duplex evolution |
Charter Communications, Inc |
| R1-2212561 |
Discussion of evaluation on NR duplex evolution |
ZTE |
| R1-2212572 |
Evaluation of NR duplex evolution |
Ericsson |
| R1-2212662 |
Summary#2 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2212663 |
Summary#3 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2212664 |
Summary#4 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2212962 |
Draft LS on interference modelling for duplex evolution |
Moderator (CMCC) |
| R1-2212963 |
LS on interference modelling for duplex evolution |
RAN1, CMCC |
| R1-2212993 |
Final summary on evaluation on NR duplex evolution |
Moderator (CMCC) |
| 9.3.2 |
Subband non-overlapping full duplex |
|
| R1-2210877 |
Discussion on potential enhancement on subband non-overlapping full duplex |
Huawei, HiSilicon |
| R1-2210932 |
Discussion for subband non-overlapping full duplex |
New H3C Technologies Co., Ltd. |
| R1-2211005 |
Discussion on subband non-overlapping full duplex |
vivo |
| R1-2211043 |
Discussion of subband non-overlapping full duplex |
ZTE |
| R1-2211065 |
Discussion on Subband non-overlapping Full Duplex |
TCL Communication Ltd. |
| R1-2211084 |
Discussion on subband non-overlapping full duplex |
Fujitsu |
| R1-2211196 |
Discussion on subband non-overlapping full duplex |
CATT |
| R1-2211233 |
Discussion on subband non-overlapping full duplex |
Spreadtrum Communications |
| R1-2211362 |
Discussion on subband non-overlapping full duplex |
xiaomi |
| R1-2211398 |
On SBFD in NR systems |
Intel Corporation |
| R1-2211485 |
Discussion on subband non-overlapping full duplex |
OPPO |
| R1-2211559 |
Discussion on subband non-overlapping full duplex enhancements |
ETRI |
| R1-2211610 |
Considerations on Subband Full Duplex TDD Operations |
Sony |
| R1-2211680 |
Discussion on subband non-overlapping full duplex |
CMCC |
| R1-2211737 |
Discussion on subband non-overlapping full duplex operations |
InterDigital, Inc. |
| R1-2211748 |
Discussion on subband non-overlapping full duplex |
NEC |
| R1-2211779 |
Subband non-overlapping full duplex |
Lenovo |
| R1-2211812 |
Views on subband non-overlapping full duplex |
Apple |
| R1-2211876 |
Discussion on subband non-overlapping full duplex |
Panasonic |
| R1-2211922 |
Study on Subband non-overlapping full duplex |
LG Electronics |
| R1-2211942 |
Subband non-overlapping full duplex |
Ericsson |
| R1-2211983 |
Discussion on subband non-overlapping full duplex |
NTT DOCOMO, INC. |
| R1-2212043 |
SBFD feasibility and design considerations for NR duplex evolution |
Samsung |
| R1-2212115 |
Feasibility and techniques for Subband non-overlapping full duplex |
Qualcomm Incorporated |
| R1-2212149 |
Discussion on subband non-overlapping full duplex |
Sharp |
| R1-2212194 |
Details of subband non-overlapping full duplex |
ASUSTeK |
| R1-2212249 |
Discussion on subband non-overlapping full duplex for NR |
MediaTek Inc. |
| R1-2212284 |
On subband non-overlapping full duplex for NR |
Nokia, Nokia Shanghai Bell |
| R1-2212289 |
Discussion on subband non-overlapping full duplex |
KDDI Corporation |
| R1-2212290 |
Discussion on subband non-overlapping full duplex |
KT Corp. |
| R1-2212334 |
Discussion on sub-band non-overlapping full duplex |
ITRI |
| R1-2212424 |
Discussion on subband non-overlapping full duplex |
CEWiT |
| R1-2212438 |
Discussion on subband non-overlapping full duplex |
WILUS Inc. |
| R1-2212733 |
Summary #1 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2212734 |
Summary #2 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2212735 |
Summary #3 of subband non-overlapping full duplex |
Moderator (CATT) |
| 9.3.3 |
Potential enhancements on dynamic/flexible TDD |
|
| R1-2210878 |
Study on potential enhancements on dynamic/flexible TDD |
Huawei, HiSilicon |
| R1-2211006 |
Potential enhancements on dynamic/flexible TDD |
vivo |
| R1-2211039 |
Study on potential enhancement on dynamic/flexible TDD |
New H3C Technologies Co., Ltd. |
| R1-2211044 |
Discussion of enhancements on dynamic/flexible TDD |
ZTE |
| R1-2211066 |
Potential enhancement on dynamic/flexible TDD |
TCL Communication Ltd. |
| R1-2211197 |
Discussion on potential enhancements on dynamic/flexible TDD |
CATT |
| R1-2211234 |
Discussion on potential enhancements on dynamic/flexible TDD |
Spreadtrum Communications |
| R1-2211363 |
Discussion on potential enhancements on dynamic/flexible TDD |
xiaomi |
| R1-2211399 |
On support of dynamic/flexible TDD in NR systems |
Intel Corporation |
| R1-2211486 |
Discussion on potential enhancements on dynamic/flexible TDD |
OPPO |
| R1-2211570 |
Potential enhancements on dynamic/flexible TDD |
Lenovo |
| R1-2211611 |
Considerations on Flexible/Dynamic TDD |
Sony |
| R1-2211681 |
Discussion on potential enhancements on flexible/dynamic TDD |
CMCC |
| R1-2211738 |
Discussion on potential enhancements on dynamic/flexible TDD |
InterDigital, Inc. |
| R1-2211747 |
Views on enhancements of dynamic/flexible TDD |
NEC |
| R1-2211813 |
Views on potential enhancements on dynamic TDD |
Apple |
| R1-2211851 |
Discussion on potential enhancements on dynamic/flexible TDD |
Panasonic |
| R1-2211923 |
Study on Potential enhancements on dynamic/flexible TDD |
LG Electronics |
| R1-2211943 |
Potential enhancements of dynamic TDD |
Ericsson |
| R1-2211984 |
Discussion on potential enhancements on dynamic/flexible TDD |
NTT DOCOMO, INC. |
| R1-2212044 |
Dynamic and flexible TDD for NR duplex evolution |
Samsung |
| R1-2212116 |
On potential enhancements on dynamic/flexible TDD |
Qualcomm Incorporated |
| R1-2212250 |
Discussion on potential enhancements on dynamic/flexible TDD |
MediaTek Inc. |
| R1-2212285 |
Dynamic TDD enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2212425 |
Discussion on enhancements on dynamic/flexible TDD |
CEWiT |
| R1-2212665 |
Summary #1 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2212666 |
Summary #2 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2212667 |
Summary #3 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2212668 |
Summary #4 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| 9.4 |
NR sidelink evolution |
|
| R1-2212846 |
Session notes for 9.4 (NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| 9.4.1.1 |
Channel access mechanism |
|
| R1-2210827 |
On Channel Access Mechanism for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2210835 |
Channel access mechanism for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2210891 |
Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2211007 |
Channel access mechanism for sidelink on unlicensed spectrum |
vivo |
| R1-2211079 |
Discussion on channel access mechanism for SL-U |
Fujitsu |
| R1-2211198 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2211235 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2211263 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2211364 |
Discussion on channel access mechanism for sidelink-unlicensed |
xiaomi |
| R1-2211400 |
Channel Access Mechanisms for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2211450 |
On channel access mechanism and resource allocation for SL-U |
OPPO |
| R1-2211514 |
Discussion of channel access mechanism for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2211560 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
ETRI |
| R1-2211579 |
Channel access mechanism for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2211612 |
Discussion on channel access mechanism for SL-unlicensed |
Sony |
| R1-2211682 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CMCC |
| R1-2211709 |
Sidelink channel access on unlicensed spectrum |
InterDigital, Inc. |
| R1-2211758 |
SL-U Channel Access Mechanism Details |
CableLabs |
| R1-2211761 |
Further Discussion on Channel Access Mechanisms |
Johns Hopkins University APL |
| R1-2211814 |
On channel access mechanism for sidelink on FR1 unlicensed spectrum |
Apple |
| R1-2211917 |
Considerations on channel access mechanism of SL-U |
CAICT |
| R1-2211985 |
Discussion on channel access mechanism in SL-U |
NTT DOCOMO, INC. |
| R1-2212045 |
On channel access mechanism for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2212117 |
Channel Access Mechanism for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2212184 |
Discussion on Channel access mechanism for NR sidelink evolution |
Sharp |
| R1-2212206 |
Discussion on channel access mechanism for SL-U |
ZTE, Sanechips |
| R1-2212222 |
Channel access mechanism for SL-U |
Ericsson |
| R1-2212270 |
Discussion on channel access mechanism |
MediaTek Inc. |
| R1-2212274 |
Sidelink channel access on unlicensed spectrum |
Panasonic |
| R1-2212287 |
Channel Access Mechanism for SL-U |
ITL |
| R1-2212363 |
Channel Access of Sidelink on Unlicensed Spectrum |
NEC |
| R1-2212439 |
Discussion on channel access mechanism for SL-U |
WILUS Inc. |
| R1-2212442 |
NR Sidelink Unlicensed Channel Access Mechanisms |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2212521 |
SL-U Channel Access Mechanism Details |
CableLabs |
| R1-2212681 |
FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212682 |
FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212683 |
FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212684 |
FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212685 |
FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212686 |
FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2212801 |
FL summary #6 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212802 |
FL summary #7 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212803 |
FL summary #8 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2212827 |
Moderator summary of discussion for LS reply on SL LBT failure indication and consistent SL LBT failure |
Moderator (vivo) |
| R1-2212828 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
Moderator (vivo) |
| 9.4.1.2 |
Physical channel design framework |
|
| R1-2210828 |
On Physical Channel Design Framework for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2210836 |
Physical channel design for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2210892 |
Physical channel design for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2211008 |
Physical channel design framework for sidelink on unlicensed spectrum |
vivo |
| R1-2211113 |
Discussion on Physical channel design framework for sidelink on unlicensed spectrum |
Hyundai Motor Company |
| R1-2211199 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2211236 |
Discussion on Physical channel design for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2211264 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2211365 |
Discussion on physical channel design for sidelink-unlicensed |
xiaomi |
| R1-2211401 |
Physical Layer Enhancements for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2211451 |
On PHY channel designs and procedures for SL-U |
OPPO |
| R1-2211515 |
Discussion of physical channel design for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2211561 |
Discussion on physical channel design framework for SL-U |
ETRI |
| R1-2211580 |
Physical layer design framework for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2211613 |
Discussion on physical channel design framework for SL-unlicensed |
Sony |
| R1-2211683 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CMCC |
| R1-2211710 |
SL U physical layer design framework |
InterDigital, Inc. |
| R1-2211762 |
Further Discussion on Physical Channel Design Framework |
Johns Hopkins University APL |
| R1-2211815 |
On Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum |
Apple |
| R1-2211986 |
Discussion on channel design framework in SL-U |
NTT DOCOMO, INC. |
| R1-2212046 |
On physical channel design framework for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2212118 |
Physical Channel Design for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2212185 |
Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum |
Sharp |
| R1-2212207 |
Discussion on physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2212223 |
PHY channel design framework for SL-U |
Ericsson |
| R1-2212271 |
Discussion on physical channel design framework |
MediaTek Inc. |
| R1-2212277 |
Physical channel design for sidelink on unlicensed spectrum |
Panasonic |
| R1-2212288 |
Physical Channel Design framework for SL-U |
ITL |
| R1-2212356 |
Discussion on physical channel design framework |
NEC |
| R1-2212440 |
Discussion on PHY channel design framework for SL-U |
WILUS Inc. |
| R1-2212443 |
NR Sidelink Unlicensed Physical Channel Design |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2212645 |
FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2212646 |
FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2212647 |
FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2212648 |
FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2212649 |
FL summary#5 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2212831 |
FL summary#6 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| 9.4.2 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R1-2210829 |
On Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2210839 |
Dynamic coexistence between NR and LTE sidelink |
FUTUREWEI |
| R1-2210893 |
Co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R1-2211009 |
Co-channel coexistence for LTE sidelink and NR sidelink |
vivo |
| R1-2211200 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CATT, GOHIGH |
| R1-2211237 |
Discussion on Co-channel coexistence for LTE sidelink and NR sidelink |
Spreadtrum Communications |
| R1-2211265 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
LG Electronics |
| R1-2211300 |
Dynamic co-channel coexistence for LTE sidelink and NR sidelink |
TOYOTA Info Technology Center, Continental Automotive Technologies GmbH |
| R1-2211366 |
Discussion on co-channel coexistence for LTE and NR sidelink |
xiaomi |
| R1-2211402 |
Design Considerations for LTE and NR Sidelink Co-Channel Coexistence |
Intel Corporation |
| R1-2211452 |
Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL |
OPPO |
| R1-2211516 |
Discussion of co-channel coexistence for LTE sidelink and NR sidelink |
Transsion Holdings |
| R1-2211562 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ETRI |
| R1-2211581 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Lenovo |
| R1-2211614 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sony |
| R1-2211684 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CMCC |
| R1-2211724 |
Co-channel coexistence for LTE sidelink and NR sidelink |
InterDigital, Inc. |
| R1-2211816 |
On Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Apple |
| R1-2211840 |
On sidelink co-channel coexistence issues |
Mitsubishi Electric RCE |
| R1-2211987 |
Discussion on co-channel coexistence of LTE-SL and NR-SL |
NTT DOCOMO, INC. |
| R1-2212047 |
On co-channel coexistence for LTE sidelink and NR sidelink |
Samsung |
| R1-2212119 |
Co-channel Coexistence Between LTE SL and NR SL |
Qualcomm Incorporated |
| R1-2212186 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sharp |
| R1-2212196 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ASUSTeK |
| R1-2212208 |
Study on co-channel coexistence for LTE sidelink and NR sidelink |
ZTE, Sanechips |
| R1-2212221 |
Co-channel coexistence between LTE sidelink and NR sidelink |
Ericsson |
| R1-2212258 |
Sidelink co-channel coexistence |
MediaTek Inc. |
| R1-2212279 |
Discussion on Sidelink Co-channel Coexistence |
Panasonic |
| R1-2212322 |
Discussion on LTE and NR sidelink co-channel coexistence |
ROBERT BOSCH GmbH |
| R1-2212364 |
Co-existence between LTE and NR sidelink |
NEC |
| R1-2212441 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
WILUS Inc. |
| R1-2212444 |
Discussion on Co-Channel Coexistence for LTE and NR Sidelink |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2212537 |
FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212538 |
FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212539 |
FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212540 |
FL Summary EoM of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212769 |
FL Summary #4 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212770 |
FL Summary #5 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| R1-2212771 |
FL Summary #6 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (Fraunhofer HHI) |
| 9.4.3 |
Enhanced sidelink operation on FR2 licensed spectrum |
|
| R1-2210830 |
On Evaluation Methodology for Sidelink in FR2 |
Nokia, Nokia Shanghai Bell |
| R1-2210894 |
Remaining issues on evaluation methodology for sidelink operation on FR2 licensed spectrum |
Huawei, HiSilicon |
| R1-2211010 |
Enhanced sidelink operation on FR2 licensed spectrum |
vivo |
| R1-2211201 |
Discussion on the evaluation methodology for enhanced sidelink operation on FR2 licensed spectrum |
CATT, GOHIGH |
| R1-2211266 |
Discussion on evaluation methodology for sidelink on FR2 licensed spectrum |
LG Electronics |
| R1-2211367 |
Discussion on updating the evaluation methodology for commercial deployment scenario |
xiaomi |
| R1-2211403 |
Remaining Details for the Evaluation Methodology for SL Operating in FR-2 Licensed Band |
Intel Corporation |
| R1-2211453 |
Discussion On remaining issues of evaluation methodology for SL operation in FR2 |
OPPO |
| R1-2211563 |
Discussion on evaluation methodology for enhanced SL operation on FR2 |
ETRI |
| R1-2211582 |
Discussion on evaluation methodology for sidelink on FR2 |
Lenovo |
| R1-2211727 |
On enhanced SL FR2 operation |
InterDigital, Inc. |
| R1-2211760 |
Further discussion on antenna model enhancements for evaluation methodology for commercial deployment scenario |
Johns Hopkins University APL |
| R1-2211817 |
Discussion on Evaluation Methodology for Sidelink Operation on FR2 Licensed Spectrum |
Apple |
| R1-2212048 |
Evaluation Methodology for Enhanced SL Operation in FR2 |
Samsung |
| R1-2212120 |
Enhanced sidelink operation on FR2 licensed spectrum |
Qualcomm Incorporated |
| R1-2212209 |
Further update on the evaluation methodology for SL on FR2 |
ZTE, Sanechips |
| R1-2212224 |
Evaluation methodology for sidelink in FR2 |
Ericsson |
| R1-2212269 |
Discussion on evaluation methodology for SL FR2 licensed spectrum |
MediaTek Inc. |
| R1-2212426 |
Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation |
CEWiT |
| R1-2212582 |
FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2212583 |
FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2212954 |
FL summary #3 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| 9.5 |
Study on expanded and improved NR positioning |
|
| R1-2212847 |
Session notes for 9.5 (Study on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2213017 |
TR 38.859 v020: Study on expanded and improved NR positioning |
Rapporteurs (Intel, CATT, Ericsson) |
| R1-2213018 |
Post-meeting Comments to Draft TR 38.859 v030: Study on expanded and improved NR positioning |
Moderator (Intel Corporation) |
| 9.5.1 |
Sidelink positioning |
|
| R1-2212713 |
Summary of discussion of reply LS on Positioning Reference Units |
Moderator (CATT) |
| R1-2212714 |
Draft Reply LS on Positioning Reference Units |
Moderator (CATT) |
| R1-2212715 |
Reply LS on Positioning Reference Units |
RAN1, CATT |
| R1-2212750 |
Moderator summary 1 on discussion of SA2 LS in R1-2210821 on RAN dependency for Ranging/Sidelink Positioning |
Moderator(xiaomi) |
| R1-2212781 |
Moderator summary 2 on discussion of SA2 LS in R1-2210821 on RAN dependency for Ranging/Sidelink Positioning |
Moderator (xiaomi) |
| R1-2212782 |
[draft] Reply LS on RAN dependency for Ranging/Sidelink Positioning |
xiaomi |
| R1-2212926 |
Reply LS on RAN dependency for Ranging/Sidelink Positioning |
RAN1, xiaomi |
| R1-2212950 |
Summary of offline discussion on bandwidth requirements on SL positioning |
Moderator (Intel Corporation) |
| 9.5.1.1 |
Evaluation of SL positioning |
|
| R1-2210831 |
Evaluation of SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2210900 |
Finalizing SL positioning evaluation |
Huawei, HiSilicon |
| R1-2211011 |
Evaluation of sidelink positioning performance |
vivo |
| R1-2211202 |
Further performance evaluation for SL positioning |
CATT, GOHIGH |
| R1-2211267 |
Discussion on evaluation of SL positioning |
LG Electronics |
| R1-2211301 |
Evaluation of latency requirements for sidelink positioning |
TOYOTA Info Technology Center |
| R1-2211368 |
Discussion on evaluation of sidelink positioning |
xiaomi |
| R1-2211404 |
Evaluations of SL positioning |
Intel Corporation |
| R1-2211446 |
Evaluation results for SL positioning |
OPPO |
| R1-2211500 |
Discussion on evaluation of SL positioning |
ZTE, CMCC |
| R1-2211506 |
Summary #1 for SL positioning evaluation |
Moderator (ZTE) |
| R1-2211507 |
Summary #2 for SL positioning evaluation |
Moderator (ZTE) |
| R1-2211615 |
Evaluation of SL positioning |
Sony |
| R1-2211720 |
Evaluation results for SL positioning |
InterDigital, Inc. |
| R1-2211739 |
SL Positioning Evaluation and Performance |
Lenovo |
| R1-2212049 |
Discussion on Evaluation for SL Positioning |
Samsung |
| R1-2212121 |
Sidelink Positioning Evaluation Assumptions and Results |
Qualcomm Incorporated |
| R1-2212379 |
Evaluation of SL positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212427 |
Evaluation results and observations on V2X and IIoT use case for sidelink positioning |
CEWiT |
| R1-2212512 |
Evaluation of NR SL positioning and ranging |
Ericsson |
| R1-2212739 |
Evaluations of SL positioning |
Intel Corporation |
| 9.5.1.2 |
Potential solutions for SL positioning |
|
| R1-2210832 |
Potential solutions for SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2210837 |
Potential solutions for sidelink positioning |
FUTUREWEI |
| R1-2210901 |
Remaining issues for SL positioning solutions |
Huawei, HiSilicon |
| R1-2211012 |
Discussion on potential solutions for sidelink positioning |
vivo |
| R1-2211203 |
Further discussion on potential solutions for SL positioning |
CATT, GOHIGH |
| R1-2211238 |
Discussion on potential solutions for SL positioning |
Spreadtrum Communications |
| R1-2211268 |
Discussion on potential solutions for SL positioning |
LG Electronics |
| R1-2211302 |
Discussion on potential solutions for sidelink positioning |
TOYOTA Info Technology Center |
| R1-2211369 |
Discussion on sidelink positioning solutions |
xiaomi |
| R1-2211405 |
Potential solutions for SL positioning |
Intel Corporation |
| R1-2211447 |
Discussion on potential solutions for SL positioning |
OPPO |
| R1-2211501 |
Discussion on potential solutions for SL positioning |
ZTE |
| R1-2211530 |
Discussion on potential solutions for sidelink positioning |
China Telecom |
| R1-2211616 |
Discussion on potential solutions for SL positioning |
Sony |
| R1-2211685 |
Discussion on potential solutions for SL positioning |
CMCC |
| R1-2211723 |
Potential solutions for SL positioning |
InterDigital, Inc. |
| R1-2211740 |
Potential SL Positioning Solutions |
Lenovo |
| R1-2211818 |
On Potential solutions for SL positioning |
Apple |
| R1-2211949 |
Discussion on potential solutions for SL positioning |
DENSO CORPORATION |
| R1-2211988 |
Discussion on potential solutions for SL positioning |
NTT DOCOMO, INC. |
| R1-2212050 |
Discussion on Potential Solutions for SL Positioning |
Samsung |
| R1-2212122 |
Potential Solutions for Sidelink Positioning |
Qualcomm Incorporated |
| R1-2212178 |
Views on potential solutions for SL positioning |
Sharp |
| R1-2212192 |
The potential solutions for sidelink positioning |
MediaTek Inc. |
| R1-2212195 |
Discussion on sidelink positioning |
ASUSTeK |
| R1-2212337 |
Potential solutions for sidelink positioning in NR |
ITL |
| R1-2212371 |
Discussion on potential solutions for SL positioning |
NEC |
| R1-2212378 |
Potential solutions for SL positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212428 |
Discussion on enhancements for sidelink based positioning |
CEWiT |
| R1-2212513 |
On potential solutions for SL positioning |
Ericsson |
| R1-2212661 |
Moderator Summary #1 on potential solutions for SL positioning |
Moderator (Qualcomm Incorporated) |
| R1-2212758 |
Moderator Summary #2 on potential solutions for SL positioning |
Moderator (Qualcomm Incorporated) |
| R1-2212900 |
Moderator Summary #3 on potential solutions for SL positioning |
Moderator (Qualcomm Incorporated) |
| R1-2212938 |
Moderator Summary #4 on potential solutions for SL positioning |
Moderator (Qualcomm Incorporated) |
| 9.5.2.1 |
Solutions for integrity of RAT dependent positioning techniques |
|
| R1-2210902 |
Remaining issues for RAT-dependent integrity |
Huawei, HiSilicon |
| R1-2211013 |
Discussion on solutions for integrity of RAT-dependent positioning |
vivo |
| R1-2211204 |
Further discussion on solutions for integrity of RAT dependent positioning techniques |
CATT |
| R1-2211311 |
Views on solutions for integrity of RAT-dependent positioning techniques |
Nokia, Nokia Shanghai Bell |
| R1-2211434 |
Discussions on Integrity for NR Positioning |
OPPO |
| R1-2211502 |
Discussion on integrity of RAT dependent positioning |
ZTE |
| R1-2211617 |
On Error Sources for Integrity of NR Positioning |
Sony |
| R1-2211686 |
Discussion on integrity for RAT-dependent positioning |
CMCC |
| R1-2211713 |
Discussions on Integrity for NR RAT-dependent Positioning |
BUPT |
| R1-2211726 |
Discussion on integrity for RAT dependent positioning techniques |
InterDigital, Inc. |
| R1-2211742 |
Integrity aspects for RAT-dependent positioning |
Lenovo |
| R1-2211989 |
Discussion on solutions for integrity of RAT dependent positioning techniques |
NTT DOCOMO, INC. |
| R1-2212051 |
Discussion on Integrity of RAT Dependent Positioning |
Samsung |
| R1-2212123 |
Integrity for RAT dependent positioning |
Qualcomm Incorporated |
| R1-2212179 |
Views on solutions for integrity of RAT dependent positioning techniques |
Sharp |
| R1-2212514 |
Error Sources characterization for integrity of RAT dependent positioning techniques |
Ericsson |
| R1-2212551 |
FL summary #1 on integrity of RAT dependent positioning techniques |
Moderator (InterDigital) |
| R1-2212722 |
FL summary #2 on integrity of RAT dependent positioning techniques |
Moderator (InterDigital) |
| R1-2212793 |
FL summary #3 on integrity of RAT dependent positioning techniques |
Moderator (InterDigital) |
| R1-2212933 |
FL summary #4 on integrity of RAT dependent positioning techniques |
Moderator (InterDigital) |
| 9.5.2.2 |
Improved accuracy based on NR carrier phase measurement |
|
| R1-2210903 |
Remaining issues for carrier phase positioning |
Huawei, HiSilicon |
| R1-2211014 |
Discussion on carrier phase measurement enhancements |
vivo |
| R1-2211100 |
High precision positioning of dual frequency carrier phase |
BUPT |
| R1-2211205 |
Further discussion on improved accuracy based on NR carrier phase measurement |
CATT |
| R1-2211259 |
Experiment and Simulation Result on Carrier Phase Based Positioning |
Locaila |
| R1-2211312 |
Views on improved accuracy based on NR carrier phase measurement |
Nokia, Nokia Shanghai Bell |
| R1-2211370 |
Improved accuracy based on NR carrier phase measurement |
xiaomi |
| R1-2211406 |
Improved positioning accuracy with NR carrier phase measurements |
Intel Corporation |
| R1-2211435 |
Discussions on Carrier Phase Measurement for NR Positioning |
OPPO |
| R1-2211503 |
Discussion on carrier phase measurement based positioning |
ZTE |
| R1-2211687 |
Discussion on carrier phase positioning |
CMCC |
| R1-2211728 |
Discussion on positioning based on NR carrier phase measurement |
InterDigital, Inc. |
| R1-2211743 |
On NR carrier phase measurements |
Lenovo |
| R1-2211924 |
Discussion on OFDM based carrier phase measurement in NR |
LG Electronics |
| R1-2211990 |
Discussion on improved accuracy based on NR carrier phase measurement |
NTT DOCOMO, INC. |
| R1-2212052 |
Discussion on NR Carrier Phase Measurement |
Samsung |
| R1-2212124 |
Phase Measurements in NR Positioning |
Qualcomm Incorporated |
| R1-2212193 |
The potential solutions for carrier phase measurement |
MediaTek Inc. |
| R1-2212359 |
Discussion on NR carrier phase positioning |
NEC |
| R1-2212380 |
NR carrier phase measurements for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212415 |
Views on NR carrier phase measurement for positioning accuracy enhancement |
IIT Kanpur, CEWiT |
| R1-2212515 |
Improved accuracy based on NR carrier phase measurement |
Ericsson |
| R1-2212519 |
Views on NR carrier phase measurement for positioning accuracy enhancement |
IIT Kanpur, CEWiT |
| R1-2212520 |
Discussion on carrier phase measurement based positioning |
ZTE |
| R1-2212545 |
FL Summary #1 for improved accuracy based on NR carrier phase measurements |
Moderator (CATT) |
| R1-2212546 |
FL Summary #2 for improved accuracy based on NR carrier phase measurements |
Moderator (CATT) |
| R1-2212547 |
FL Summary #3 for improved accuracy based on NR carrier phase measurements |
Moderator (CATT) |
| R1-2212550 |
Discussion on NR Carrier Phase Measurement |
Samsung |
| R1-2212859 |
Discussion on NR Carrier Phase Measurement |
Samsung |
| R1-2212937 |
FL Summary #4 for improved accuracy based on NR carrier phase measurements |
Moderator (CATT) |
| 9.5.2.3 |
LPHAP (Low Power High Accuracy Positioning) |
|
| R1-2210904 |
Remaining issues for LPHAP |
Huawei, HiSilicon |
| R1-2211015 |
Discussion on Low Power High Accuracy Positioning |
vivo |
| R1-2211055 |
Discussions and evaluation of LPHAP enhancements |
FUTUREWEI |
| R1-2211206 |
Further discussion on Low Power High Accuracy Positioning |
CATT |
| R1-2211239 |
Discussion on evaluation and solutions for LPHAP |
Spreadtrum Communications |
| R1-2211313 |
Views on LPHAP |
Nokia, Nokia Shanghai Bell |
| R1-2211371 |
Discussion on Low Power High Accuracy Positioning |
xiaomi |
| R1-2211407 |
On Low Power High Accuracy Positioning |
Intel Corporation |
| R1-2211436 |
Discussion on Low Power High Accuracy Positioning |
OPPO |
| R1-2211504 |
Discussion on low power high accuracy positioning |
ZTE |
| R1-2211618 |
Views on Low Power High Accuracy Positioning |
Sony |
| R1-2211688 |
Discussion on low power high accuracy positioning |
CMCC |
| R1-2211730 |
Discussions on Low Power High Accuracy Positioning (LPHAP) techniques |
InterDigital, Inc. |
| R1-2211744 |
LPHAP considerations |
Lenovo |
| R1-2211925 |
Discussion on LPHAP in idle/inactive state |
LG Electronics |
| R1-2211991 |
Discussion on Low Power High Accuracy Positioning |
NTT DOCOMO, INC. |
| R1-2212053 |
Discussion on LPHAP |
Samsung |
| R1-2212125 |
Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning |
Qualcomm Incorporated |
| R1-2212516 |
Evaluations for Low Power High Accuracy Positioning |
Ericsson |
| R1-2212690 |
Summary #1 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2212691 |
Summary #2 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2212692 |
Summary #3 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2212723 |
Summary #1 of LPHAP information delivery to RAN |
Moderator (Huawei) |
| R1-2212724 |
Draft Reply LS on LPHAP information delivery to RAN |
Moderator (Huawei) |
| R1-2212725 |
Reply LS on LPHAP information delivery to RAN |
RAN1, Huawei |
| R1-2212726 |
Summary #1 of SRS in multiple cells |
Moderator (Huawei) |
| R1-2212727 |
Draft Reply LS on SRS in multiple cells |
Moderator (Huawei) |
| R1-2212728 |
Reply LS on SRS in multiple cells |
RAN1, Huawei |
| R1-2212928 |
Summary #4 for low power high accuracy positioning |
Moderator (CMCC) |
| 9.5.3 |
Positioning for RedCap UEs |
|
| R1-2210905 |
Remaining issues of RedCap positioning |
Huawei, HiSilicon |
| R1-2210921 |
Discussion on Positioning for RedCap UEs |
Quectel |
| R1-2211016 |
Discussion on positioning for RedCap UEs |
vivo |
| R1-2211207 |
Further discussion on positioning for RedCap UEs |
CATT |
| R1-2211314 |
Views on Positioning for RedCap UEs |
Nokia, Nokia Shanghai Bell |
| R1-2211408 |
Enhancements for positioning for RedCap UEs |
Intel Corporation |
| R1-2211437 |
Discussion on Positioning for RedCap Ues |
OPPO |
| R1-2211505 |
Discussion on Positioning for RedCap UE |
ZTE |
| R1-2211619 |
Views on positioning for RedCap UEs |
Sony |
| R1-2211689 |
Discussion on RedCap positioning |
CMCC |
| R1-2211732 |
Discussions on positioning for RedCap UEs |
InterDigital, Inc. |
| R1-2211741 |
Public Safety Personal Protection Equipment (PPE) |
FirstNet, AT&T, UK Home Office, Erillisverkot, MINISTERE DE L’INTERIEUR, SyncTechno Inc., Softil, Nkom |
| R1-2211745 |
Positioning for RedCap devices |
Lenovo |
| R1-2211819 |
On Positioning for RedCap UEs |
Apple |
| R1-2211926 |
Discussion on positioning support for RedCap Ues |
LG Electronics |
| R1-2211992 |
Discussion on positioning for RedCap UEs |
NTT DOCOMO, INC. |
| R1-2212054 |
Discussion on Positioning for RedCap UEs |
Samsung |
| R1-2212126 |
Positioning for Reduced Capabilities UEs |
Qualcomm Incorporated |
| R1-2212180 |
Views on positioning for RedCap UEs |
Sharp |
| R1-2212197 |
The potential solutions for RedCap UEs for positioning |
MediaTek Inc. |
| R1-2212368 |
Discussion on positioning support for RedCap UEs |
NEC |
| R1-2212517 |
Positioning for RedCap Ues |
Ericsson |
| R1-2212601 |
Feature lead summary #1 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2212602 |
Feature lead summary #2 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2212603 |
Feature lead summary #3 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2212743 |
Discussion on Positioning for RedCap UE |
ZTE |
| R1-2212949 |
Feature lead summary #4 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| 9.6 |
Enhanced support of reduced capability NR device |
|
| R1-2212848 |
Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) |
Ad-hoc Chair (CMCC) |
| R1-2212982 |
RAN1 agreements for Rel-18 NR RedCap |
Rapporteur (Ericsson) |
| 9.6.1 |
UE complexity reduction |
|
| R1-2210833 |
Continued discussion on R18 RedCap complexity techniques |
FUTUREWEI |
| R1-2210868 |
Discussion on potential solutions to further reduce UE complexity |
Huawei, HiSilicon |
| R1-2211017 |
Discussion on UE further complexity reduction |
vivo, Guangdong Genius |
| R1-2211099 |
UE complexity reduction for eRedCap |
Panasonic |
| R1-2211208 |
Discussion on further complexity reduction for eRedCap UE |
CATT |
| R1-2211240 |
Discussion on enhanced support of RedCap devices |
Spreadtrum Communications, H3C |
| R1-2211372 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2211409 |
Discussion on complexity reduction for eRedCap UE |
Intel Corporation |
| R1-2211470 |
Technologies for further reduced UE complexity |
OPPO |
| R1-2211517 |
Discussion on UE complexity reduction |
Transsion Holdings |
| R1-2211531 |
Discussion on UE complexity reduction |
China Telecom |
| R1-2211571 |
UE complexity reduction |
Lenovo |
| R1-2211620 |
UE complexity reduction for eRedCap |
Sony |
| R1-2211690 |
Discussion on further UE complexity reduction |
CMCC |
| R1-2211757 |
Further RedCap UE complexity reduction |
Ericsson |
| R1-2211759 |
RedCap UE Complexity Reduction |
Nokia, Nokia Shanghai Bell |
| R1-2211820 |
Further RedCap UE complexity reduction |
Apple |
| R1-2211850 |
Considerations for further UE complexity reduction |
Sierra Wireless. S.A. |
| R1-2211856 |
Discussion on UE complexity reduction |
Sharp |
| R1-2211875 |
Discussion on Rel-18 RedCap UE |
NEC |
| R1-2211902 |
Discussion on further UE complexity reduction |
ZTE, Sanechips |
| R1-2211993 |
Discussion on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2212055 |
Further UE complexity reduction for eRedCap |
Samsung |
| R1-2212127 |
UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2212175 |
Discussion on UE complexity reduction |
DENSO CORPORATION |
| R1-2212246 |
On eRedCap UE complexity reduction |
MediaTek Inc. |
| R1-2212300 |
Discussion on further UE complexity reduction for eRedCap |
LG Electronics |
| R1-2212416 |
On further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2212533 |
FL summary #1 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2212534 |
FL summary #2 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2212535 |
FL summary #3 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2212536 |
FL summary #4 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| 9.7 |
Study on network energy savings for NR |
|
| R1-2212483 |
TR 38.864 update for study on network energy savings for NR |
Rapporteur (Huawei) |
| R1-2213007 |
TR 38.864 update for study on network energy savings for NR |
Rapporteur (Huawei) |
| R1-2213014 |
Comments collection for updated draft TR 38.864 post RAN1#111 |
Moderator (Huawei) |
| 9.7.1 |
NW energy savings performance evaluation |
|
| R1-2210858 |
Evaluation results and other performance aspects for network energy savings |
Huawei, HiSilicon |
| R1-2211018 |
Discussions on NW energy savings performance evaluation |
vivo |
| R1-2211085 |
Discussion on NW energy saving performance evaluation |
Fujitsu |
| R1-2211097 |
NW energy savings performance evaluation |
Nokia, Nokia Shanghai Bell |
| R1-2211209 |
Remaining Issues of Evaluation Methodology and Power Model for Network Energy Saving |
CATT |
| R1-2211241 |
Discussion on performance evaluation of network energy savings |
Spreadtrum Communications |
| R1-2211410 |
Discussion on Network energy saving performance evaluations |
Intel Corporation |
| R1-2211458 |
Discussion on NW energy savings performance evaluation |
OPPO |
| R1-2211691 |
Discussion on network energy saving performance evaluation |
CMCC |
| R1-2211845 |
Performance evaluation for network energy saving |
InterDigital, Inc. |
| R1-2211903 |
Evaluation results of NW energy saving techniques |
ZTE, Sanechips |
| R1-2211994 |
Discussion on NW energy saving performance evaluation |
NTT DOCOMO, INC. |
| R1-2212056 |
NW energy savings performance evaluation |
Samsung |
| R1-2212128 |
NW energy savings performance evaluation |
Qualcomm Incorporated |
| R1-2212154 |
Evaluations for network energy savings techniques |
Ericsson |
| R1-2212259 |
NW energy savings performance evaluation |
MediaTek Inc. |
| R1-2212301 |
Discussion on performance evaluation for network energy savings |
LG Electronics |
| R1-2212541 |
Discussions on NW energy savings performance evaluation |
vivo |
| R1-2212543 |
NW energy savings performance evaluation |
Samsung |
| R1-2212563 |
Discussion on Network energy saving performance evaluations |
Intel Corporation |
| R1-2212653 |
NW energy savings performance evaluation |
Qualcomm Incorporated |
| R1-2212702 |
FL summary#1 for NW Energy Savings |
Moderator (Huawei) |
| R1-2212703 |
FL summary#2 for NW Energy Savings |
Moderator (Huawei) |
| R1-2212738 |
Evaluation results of NW energy saving techniques |
ZTE, Sanechips |
| R1-2212745 |
NW energy savings performance evaluation |
Qualcomm Incorporated |
| R1-2212934 |
NW energy savings performance evaluation |
Qualcomm Incorporated |
| R1-2212935 |
FL summary#3 for NW Energy Savings |
Moderator (Huawei) |
| R1-2213000 |
NW energy savings performance evaluation |
Qualcomm Incorporated |
| R1-2213006 |
FL summary for Post-110-R18- NW_ES2 |
Moderator (Huawei) |
| R1-2213013 |
Simulation results summary for NW Energy Savings |
Moderator (Huawei) |
| 9.7.2 |
Network energy saving techniques |
|
| R1-2210852 |
Network Energy Saving Techniques |
FUTUREWEI |
| R1-2210859 |
On techniques aspects for network energy savings |
Huawei, HiSilicon |
| R1-2211019 |
Discussion on NW energy saving technique |
vivo |
| R1-2211086 |
Discussion on network energy saving techniques |
Fujitsu |
| R1-2211098 |
Network energy saving techniques |
Nokia, Nokia Shanghai Bell |
| R1-2211210 |
Network Energy Saving techniques in time, frequency, and spatial domain |
CATT |
| R1-2211242 |
Discussion on network energy saving techniques |
Spreadtrum Communications |
| R1-2211373 |
Discussions on techniques for network energy saving |
xiaomi |
| R1-2211411 |
Discussion on Network Energy Saving Techniques |
Intel Corporation |
| R1-2211459 |
Discussion on network energy saving techniques |
OPPO |
| R1-2211518 |
Discussion on network energy saving techniques |
Transsion Holdings |
| R1-2211532 |
Discussion on the network energy saving techniques |
China Telecom |
| R1-2211598 |
Discussion on potential network energy saving techniques |
Panasonic |
| R1-2211692 |
Discussion on network energy saving techniques |
CMCC |
| R1-2211751 |
Discussion on network energy saving techniques |
NEC |
| R1-2211780 |
Network energy saving techniques |
Lenovo |
| R1-2211821 |
Discussion on network energy saving techniques |
Apple |
| R1-2211846 |
Potential techniques for network energy saving |
InterDigital, Inc. |
| R1-2211904 |
Discussion on NW energy saving techniques |
ZTE, Sanechips |
| R1-2211938 |
Views on the scope for Rel. 18 network energy saving techniques |
AT&T |
| R1-2211995 |
Discussion on NW energy saving techniques |
NTT DOCOMO, INC. |
| R1-2212057 |
Network energy saving techniques |
Samsung |
| R1-2212129 |
Network energy saving techniques |
Qualcomm Incorporated |
| R1-2212155 |
Network energy savings techniques |
Ericsson |
| R1-2212260 |
Network energy saving techniques |
MediaTek Inc. |
| R1-2212302 |
Discussion on physical layer techniques for network energy savings |
LG Electronics |
| R1-2212315 |
Discussion on network energy saving techniques |
Rakuten Symphony |
| R1-2212335 |
Discussion on potential L1 network energy saving techniques for NR |
ITRI |
| R1-2212381 |
On Network Energy Saving Techniques |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2212429 |
Discussion on Network energy saving techniques |
CEWiT |
| R1-2212564 |
Discussion Summary #1 for energy saving techniques of NW energy saving SI |
Moderator (Intel Corporation) |
| R1-2212565 |
Discussion Summary #2 for energy saving techniques of NW energy saving SI |
Moderator (Intel Corporation) |
| R1-2212765 |
Discussion on Network energy saving techniques |
CEWiT |
| R1-2212779 |
Discussion Summary #3 for energy saving techniques of NW energy saving SI |
Moderator (Intel Corporation) |
| R1-2212780 |
Discussion Summary #4 for energy saving techniques of NW energy saving SI |
Moderator (Intel Corporation) |
| R1-2212814 |
Discussion on Network energy saving techniques |
CEWiT |
| 9.8 |
NR network-controlled repeaters |
|
| R1-2212886 |
Summary#1 of discussion on the reply LS to RAN4 |
Moderator (CMCC) |
| R1-2212887 |
[Draft] Reply LS to RAN4 on NCR-MT transmission and Beam correspondence |
Moderator (CMCC) |
| R1-2212910 |
Reply LS to RAN4 on NCR-MT transmission and Beam correspondence |
RAN1, CMCC |
| 9.8.1 |
Side control information and NCR behavior |
|
| R1-2210882 |
Side control information and behaviors for network-controlled repeaters |
Huawei, HiSilicon |
| R1-2211020 |
Discussion on side control information to enable NR network-controlled repeaters |
vivo |
| R1-2211080 |
Discussion on side control information and NCR behavior |
Fujitsu |
| R1-2211107 |
Discussion on side control information for NCR |
ZTE |
| R1-2211211 |
Discussion on side control information and NCR behavior |
CATT |
| R1-2211243 |
Discussion on side control information and NCR behavior |
Spreadtrum Communications |
| R1-2211303 |
Discussion on side control information and NCR behavior |
Nokia, Nokia Shanghai Bell |
| R1-2211317 |
Discussions on side control information and NCR behavior |
InterDigital, Inc. |
| R1-2211374 |
Discussion on side control information and NCR behavior |
xiaomi |
| R1-2211412 |
Discussion on Side control information to enable NR network-controlled repeater |
Intel Corporation |
| R1-2211533 |
Discussion on side control information and NCR behaviour |
China Telecom |
| R1-2211564 |
Discussion on side control information for network-controlled repeater |
ETRI |
| R1-2211602 |
Discussion on side control information and NCR behavior |
Panasonic |
| R1-2211621 |
Aspects of side control information and NCR behavior |
Sony |
| R1-2211693 |
Discussion on side control information and NCR behavior |
CMCC |
| R1-2211822 |
On side control information and NCR behavior |
Apple |
| R1-2211877 |
Side information on NCR beams and forwarding behaviors |
Sharp |
| R1-2211882 |
Discussion on side control information and NCR behaviour |
Lenovo |
| R1-2211927 |
Discussion on side control information and NCR behavior |
LG Electronics |
| R1-2211935 |
Signalling support for NR network-controlled repeaters |
AT&T |
| R1-2211996 |
Discussion on Side control information and NCR behavior |
NTT DOCOMO, INC. |
| R1-2212058 |
Discussion on side control information and NCR behavior |
Samsung |
| R1-2212130 |
On side control information and NCR behavior |
Qualcomm Incorporated |
| R1-2212244 |
Side control information and NCR behavior |
MediaTek Inc. |
| R1-2212286 |
Discussion on side control information and NCR behavior |
KDDI Corporation |
| R1-2212291 |
Discussion on side control information and NCR behaviour |
KT Corp. |
| R1-2212314 |
Discussion on side control information for NCR |
Rakuten Mobile, Inc |
| R1-2212323 |
Discussion on side control information and NCR behavior |
NICT and Toyota InfoTechnology Center |
| R1-2212344 |
Side-control information and NCR behavior |
Ericsson |
| R1-2212369 |
Discussion on side control information and NCR behaviour |
NEC |
| R1-2212430 |
Discussion on signaling side control information and NCR behavior |
CEWiT, IITK |
| R1-2212590 |
Summary#1 of discussion on side control information |
Moderator (ZTE) |
| R1-2212605 |
Summary#2 of discussion on side control information |
Moderator (ZTE) |
| R1-2212785 |
Summary#3 of discussion on side control information |
Moderator (ZTE) |
| R1-2212786 |
Summary#4 of discussion on side control information |
Moderator (ZTE) |
| 9.8.2 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
|
| R1-2210883 |
Other aspects of network-controlled repeaters |
Huawei, HiSilicon |
| R1-2211021 |
Discussion on signaling for side control information |
vivo |
| R1-2211081 |
Discussion on control plane signaling and procedures relevant to RAN1 |
Fujitsu |
| R1-2211108 |
Discussion on other aspects for NCR |
ZTE |
| R1-2211212 |
Discussion on control plane signalling and procedures for NR network-controlled repeaters |
CATT |
| R1-2211304 |
Discussion on other aspects including control plane signalling and procedures relevant to RAN1 |
Nokia, Nokia Shanghai Bell |
| R1-2211318 |
Discussion on control plane signaling and procedures for network-controlled repeaters |
InterDigital, Inc. |
| R1-2211375 |
Discussion on other aspects of NCR |
xiaomi |
| R1-2211413 |
Discussions on L1/L2 signaling and configuration for side control information |
Intel Corporation |
| R1-2211511 |
Discussion on other aspects including control plane signalling and procedures for NCR |
IIT-K, CEWiT |
| R1-2211565 |
Discussion on NCR signaling and procedures |
ETRI |
| R1-2211622 |
Aspects of signaling and control procedures relevant to RAN1 |
Sony |
| R1-2211632 |
Discussion on NCR control plane signalling and procedures |
Panasonic |
| R1-2211694 |
Discussion on other aspects including control plane signalling and procedures relevant to RAN1 |
CMCC |
| R1-2211763 |
Discussion on NCR control information signalling and procedures |
Lenovo |
| R1-2211823 |
On control plane signaling and procedures for NCR |
Apple |
| R1-2211918 |
Discussion on other aspects of NCR |
CAICT |
| R1-2211928 |
Discussion on other aspects for NCR |
LG Electronics |
| R1-2211997 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
NTT DOCOMO, INC. |
| R1-2212059 |
On signaling and procedures for network-controlled repeaters |
Samsung |
| R1-2212131 |
On other NCR aspects |
Qualcomm Incorporated |
| R1-2212319 |
Discussion on other aspects for NCR |
Rakuten Mobile, Inc |
| R1-2212345 |
Other aspects including control signaling and procedures in NCR |
Ericsson |
| R1-2212370 |
Discussion on other aspects for network-controlled repeaters |
NEC |
| R1-2212552 |
Summary#1 on other aspects |
Moderator (Fujitsu) |
| R1-2212705 |
Summary#2 on other aspects |
Moderator (Fujitsu) |
| 9.9.1 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
|
| R1-2210856 |
Discussion on multi-cell scheduling with a single DCI |
Huawei, HiSilicon |
| R1-2210924 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
Nokia, Nokia Shanghai Bell |
| R1-2211022 |
Discussion on multi-cell scheduling |
vivo |
| R1-2211045 |
Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI |
ZTE |
| R1-2211063 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Google Inc. |
| R1-2211082 |
Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Fujitsu |
| R1-2211213 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CATT |
| R1-2211244 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Spreadtrum Communications |
| R1-2211376 |
Discussion on the remaining issues for the multi-cell scheduling with a single DCI |
xiaomi |
| R1-2211414 |
Discussions on multi-cell scheduling with a single DCI |
Intel Corporation |
| R1-2211488 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
OPPO |
| R1-2211534 |
Discussion on multi-cell scheduling with a single DCI |
China Telecom |
| R1-2211585 |
On multi-cell scheduling via a single DCI |
Lenovo |
| R1-2211695 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CMCC |
| R1-2211824 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
Apple |
| R1-2211878 |
Discussion on Multicarrier scheduling with a single DCI |
FGI |
| R1-2211919 |
Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CAICT |
| R1-2211998 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
NTT DOCOMO, INC. |
| R1-2212060 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2212132 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Qualcomm Incorporated |
| R1-2212156 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Ericsson |
| R1-2212190 |
Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Langbo |
| R1-2212252 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
MediaTek Inc. |
| R1-2212303 |
Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI |
LG Electronics |
| R1-2212336 |
Discussion on multi-cell scheduling with a single DCI |
ITRI |
| R1-2212362 |
Discussion on Multi-cell PXSCH scheduling with a single DCI |
NEC |
| R1-2212392 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2212393 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2212394 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2212923 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2212924 |
Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| 9.9.2 |
Multi-carrier UL Tx switching scheme |
|
| R1-2210857 |
Discussion on multi-carrier UL Tx switching |
Huawei, HiSilicon |
| R1-2211023 |
Discussion on UL TX switching |
vivo |
| R1-2211046 |
Discussion on Multi-carrier UL Tx switching scheme |
ZTE |
| R1-2211064 |
Discussion on multi-carrier UL Tx switching scheme |
Google Inc. |
| R1-2211214 |
Discussion on multi-carrier UL Tx switching scheme |
CATT |
| R1-2211245 |
Discussion on multi-carrier UL Tx switching scheme |
Spreadtrum Communications |
| R1-2211285 |
On Multi-Carrier UL Tx Switching |
Nokia, Nokia Shanghai Bell |
| R1-2211377 |
Discussion on multi-carrier UL Tx switching scheme |
xiaomi |
| R1-2211489 |
Discussion on multi-carrier UL Tx switching scheme |
OPPO |
| R1-2211535 |
Discussion on UL Tx switching across up to 3 or 4 bands |
China Telecom |
| R1-2211623 |
Considerations on Multi-carrier UL Tx switching scheme |
Sony |
| R1-2211696 |
Discussion on multi-carrier UL Tx switching scheme |
CMCC |
| R1-2211825 |
On multi-carrier UL Tx switching |
Apple |
| R1-2211999 |
Discussion on Multi-carrier UL Tx switching scheme |
NTT DOCOMO, INC. |
| R1-2212061 |
On multi-carrier UL Tx switching |
Samsung |
| R1-2212133 |
Discussion on Rel-18 UL Tx switching |
Qualcomm Incorporated |
| R1-2212157 |
Multi-carrier UL Tx switching |
Ericsson |
| R1-2212251 |
On multi-carrier UL Tx switching scheme |
MediaTek Inc. |
| R1-2212304 |
Discussion on Multi-carrier UL Tx switching scheme |
LG Electronics |
| R1-2212528 |
Summary#1 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2212757 |
Summary#2 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2212879 |
Summary#3 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2212894 |
Summary#4 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| 9.10 |
Study on XR enhancements for NR |
|
| R1-2212408 |
Work Plan for Rel-18 SI on XR Enhancements for NR |
Rapporteur (Nokia, Qualcomm) |
| R1-2212855 |
Draft reply LS on XR and Media Services |
vivo |
| R1-2212967 |
Draft reply LS on XR and Media Services |
vivo |
| R1-2212994 |
Reply LS on XR and Media Services |
RAN1, vivo |
| R1-2213015 |
Text Proposal for TR 38.835 |
Rapporteurs (Nokia, Qualcomm) |
| R1-2213016 |
LS to capture Text Proposal for TR 38.835 |
RAN1, Nokia |
| 9.10.1 |
XR specific power saving techniques |
|
| R1-2210906 |
Discussion on XR-specific power saving techniques |
Huawei, HiSilicon |
| R1-2210922 |
Discussion on power saving enhancements for XR |
Ericsson |
| R1-2211024 |
Discussion on XR specific power saving enhancements |
vivo |
| R1-2211174 |
UE Power saving techniques for XR |
CATT |
| R1-2211246 |
Discussion on XR specific power saving techniques |
Spreadtrum Communications |
| R1-2211341 |
Discussions on techniques for XR Power Saving |
xiaomi |
| R1-2211389 |
Discussion on XR specific power saving techniques |
Intel Corporation |
| R1-2211490 |
Discussion on XR specific power saving techniques |
OPPO |
| R1-2211536 |
Discussion on XR specific power saving enhancement for NR |
China Telecom |
| R1-2211539 |
XR specific power saving techniques |
TCL Communication Ltd. |
| R1-2211551 |
XR-specific power saving enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2211566 |
Discussion on XR-specific power saving techniques |
ETRI |
| R1-2211624 |
Discussion on XR-specific power saving techniques |
Sony |
| R1-2211653 |
Discussion on XR specific power saving techniques |
Panasonic |
| R1-2211697 |
Discussion on XR-specific power saving techniques |
CMCC |
| R1-2211752 |
Discussion on XR specific power saving techniques |
NEC |
| R1-2211781 |
XR-specific power saving techniques |
Lenovo |
| R1-2211826 |
On XR specific power saving techniques |
Apple |
| R1-2211842 |
Discussion on XR specific power saving techniques |
InterDigital, Inc. |
| R1-2211905 |
Evaluation on XR specific power saving techniques |
ZTE, Sanechips |
| R1-2211920 |
Further Discussion on XR power saving |
III |
| R1-2212000 |
Discussion on XR specific power saving techniques |
NTT DOCOMO, INC. |
| R1-2212062 |
Considerations on Power Savings for XR |
Samsung |
| R1-2212134 |
Power saving techniques for XR |
Qualcomm Incorporated |
| R1-2212253 |
On XR specific power saving techniques |
MediaTek Inc. |
| R1-2212305 |
Discussion on XR-specific power saving techniques |
LG Electronics |
| R1-2212387 |
On XR-specific power saving techniques |
Google Inc. |
| R1-2212518 |
Discussion on XR specific power saving enhancements |
vivo |
| R1-2212596 |
Evaluation on XR specific power saving techniques |
ZTE, Sanechips |
| R1-2212698 |
Moderator Summary#1 on XR specific power saving techniques |
Moderator (Qualcomm Incorporated) |
| R1-2212699 |
Moderator Summary#2 on XR specific power saving techniques |
Moderator (Qualcomm Incorporated) |
| R1-2212700 |
Moderator Summary#3 on XR specific power saving techniques |
Moderator (Qualcomm Incorporated) |
| R1-2212701 |
Final Moderator Summary on XR specific power saving techniques |
Moderator (Qualcomm Incorporated) |
| R1-2212860 |
[Draft] TR 38.835 - TP for power saving evaluation results |
Rapporteur (Qualcomm) |
| 9.10.2 |
XR-specific capacity enhancements techniques |
|
| R1-2210849 |
XR Capacity Evaluation and Enhancements |
FUTUREWEI |
| R1-2210907 |
Discussion on XR-specific capacity enhancements techniques |
Huawei, HiSilicon |
| R1-2210923 |
Discussion on capacity enhancements for XR |
Ericsson |
| R1-2211025 |
Discussion on XR specific capacity enhancements |
vivo |
| R1-2211175 |
NR enhancement for XR capacity improvement |
CATT |
| R1-2211415 |
Discussion on XR specific capacity enhancement techniques |
Intel Corporation |
| R1-2211491 |
Discussion on XR specific capacity enhancements techniques |
OPPO |
| R1-2211540 |
XR-specific capacity enhancements techniques |
TCL Communication Ltd. |
| R1-2211552 |
XR-specific capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2211625 |
XR-specific capacity enhancements and evaluation results |
Sony |
| R1-2211654 |
Discussion on XR capacity enhancement techniques |
Panasonic |
| R1-2211698 |
Discussion on XR-specific capacity enhancements techniques |
CMCC |
| R1-2211782 |
XR-specific Capacity Enhancement Techniques |
Lenovo |
| R1-2211827 |
On XR-specific capacity enhancements techniques |
Apple |
| R1-2211843 |
Discussion on XR-specific capacity enhancements techniques |
InterDigital, Inc. |
| R1-2211906 |
XR specific capacity enhancements |
ZTE, Sanechips |
| R1-2212001 |
Discussion on XR specific capacity improvement enhancements |
NTT DOCOMO, INC. |
| R1-2212063 |
Considerations on Capacity Improvements for XR |
Samsung |
| R1-2212135 |
Capacity enhancement techniques for XR |
Qualcomm Incorporated |
| R1-2212254 |
On XR specific capacity improvement enhancement |
MediaTek Inc. |
| R1-2212275 |
Discussion on XR-specific capacity enhancements techniques |
KT Corp. |
| R1-2212306 |
Discussion on XR-specific capacity enhancement techniques |
LG Electronics |
| R1-2212365 |
Discussion on XR-specific capacity enhancements |
NEC |
| R1-2212386 |
On XR-specific capacity enhancements techniques |
Google Inc. |
| R1-2212407 |
[Draft] TR 38.835 - TP for Capacity evaluation results |
Rapporteur (Nokia) |
| R1-2212595 |
Discussion on XR specific capacity enhancements |
vivo |
| R1-2212606 |
Moderator Summary#1 - Study on XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2212607 |
Moderator Summary#2 - Study on XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2212608 |
Moderator Summary#3 - Study on XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2212609 |
Moderator Summary#4 - Study on XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2212650 |
Discussion on XR-specific capacity enhancements techniques |
Huawei, HiSilicon |
| R1-2212732 |
[Draft] TR 38.835 - TP for Capacity evaluation results |
Rapporteur (Nokia) |
| R1-2212936 |
[Draft] TR 38.835 - TP for Capacity evaluation results |
Rapporteur (Nokia) |
| 9.11 |
NTN (Non-Terrestrial Networks) enhancements |
|
| R1-2210953 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R1-2212744 |
Discussion on how to reply to RAN2 LS on RACH-less handover in NTN |
Moderator (OPPO) |
| R1-2212809 |
[Draft] reply LS on RACH-less handover in NTN |
OPPO |
| R1-2212849 |
Session notes for 9.11 (NTN (Non-Terrestrial Networks) enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2212930 |
[Draft] reply LS on RACH-less handover in NTN |
OPPO |
| R1-2212997 |
[Draft] reply LS on RACH-less handover in NTN |
OPPO |
| R1-2213001 |
Reply LS on RACH-less handover in NTN |
RAN1, OPPO |
| 9.11.1 |
Coverage enhancement for NR NTN |
|
| R1-2210872 |
Discussion on coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2211026 |
Discussions on coverage enhancements for NR NTN |
vivo |
| R1-2211093 |
Coverage enhancement for NR NTN |
MediaTek Inc. |
| R1-2211109 |
Discussion on coverage enhancement for NTN |
ZTE |
| R1-2211115 |
Discussion on coverage enhancement for NR NTN |
Hyundai Motor Company |
| R1-2211176 |
Further discussion on UL coverage enhancement for NR NTN |
CATT |
| R1-2211247 |
Discussion on coverage enhancements for NTN |
Spreadtrum Communications |
| R1-2211328 |
Discussion on DMRS bundling for NR NTN |
NTPU |
| R1-2211342 |
Discussion on coverage enhancement for NR-NTN |
xiaomi |
| R1-2211416 |
On coverage enhancement for NR NTN |
Intel Corporation |
| R1-2211460 |
Discussion on coverage enhancement for NR NTN |
OPPO |
| R1-2211567 |
Discussion on coverage enhancement for NR NTN |
ETRI |
| R1-2211594 |
Discussion on coverage enhancement for NR-NTN |
Panasonic |
| R1-2211626 |
On coverage enhancement for NR NTN |
Sony |
| R1-2211699 |
Discussion on coverage enhancement for NR NTN |
CMCC |
| R1-2211754 |
Coverage enhancement for NR NTN |
NEC |
| R1-2211828 |
Discussion on Coverage Enhancement for NR NTN |
Apple |
| R1-2211883 |
Discussion on coverage enhancement for NR NTN |
Lenovo |
| R1-2211929 |
Discussion on coverage enhancement for NR NTN |
LG Electronics |
| R1-2212002 |
Discussion on coverage enhancement for NR NTN |
NTT DOCOMO, INC. |
| R1-2212064 |
On coverage enhancement for NR NTN |
Samsung |
| R1-2212136 |
Coverage enhancements for NR NTN |
Qualcomm Incorporated |
| R1-2212213 |
Discussion on coverage enhancement for NR NTN |
Baicells |
| R1-2212240 |
Coverage enhancement for NR NTN |
MediaTek Inc. |
| R1-2212325 |
On coverage enhancements for NR NTN |
Ericsson |
| R1-2212401 |
Considerations on coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2212569 |
Summary #1 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2212570 |
Summary #2 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2212571 |
Summary #3 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2212864 |
Summary #4 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2212865 |
Summary #5 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| 9.11.2 |
Network verified UE location for NR NTN |
|
| R1-2210873 |
Discussion on network-verified UE location for NR NTN |
Huawei, HiSilicon |
| R1-2210948 |
Discussion on network verified UE location in NR NTN |
THALES |
| R1-2210949 |
FL Summary #1: Network verified UE location for NR NTN |
THALES |
| R1-2210950 |
FL Summary #2: Network verified UE location for NR NTN |
THALES |
| R1-2210951 |
FL Summary #3: Network verified UE location for NR NTN |
THALES |
| R1-2210952 |
FL Summary #4: Network verified UE location for NR NTN |
THALES |
| R1-2211027 |
Discussions on UE location verification in NR NTN |
vivo |
| R1-2211094 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2211110 |
Discussion on network verified UE location for NR NTN |
ZTE |
| R1-2211177 |
Further evaluations on network verified UE location for NR NTN |
CATT |
| R1-2211343 |
Discussion on the network verified location |
xiaomi |
| R1-2211417 |
On network verified UE location for NR NTN |
Intel Corporation |
| R1-2211461 |
Discussion on network verified UE location for NR NTN |
OPPO |
| R1-2211601 |
Discussion on Network-verified UE location for NTN |
PANASONIC |
| R1-2211627 |
Network verified UE location for NR NTN |
Sony |
| R1-2211746 |
NTN NW verified UE location |
Lenovo |
| R1-2211765 |
On network verified UE location in NR NTN |
Ericsson Limited |
| R1-2211829 |
On Network Verified UE Location |
Apple |
| R1-2211930 |
Discussion on network verified UE location for NR NTN |
LG Electronics |
| R1-2212003 |
Discussion on Network verified UE location for NR NTN |
NTT DOCOMO, INC. |
| R1-2212065 |
Network verified UE location for NR NTN |
Samsung |
| R1-2212137 |
Network verified UE location for NR NTN |
Qualcomm Incorporated |
| R1-2212241 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2212402 |
Further discussion on Network Verified UE Positioning |
Nokia, Nokia Shanghai Bell |
| 9.11.3 |
Disabling of HARQ feedback for IoT NTN |
|
| R1-2210874 |
Discussion on disabling of HARQ feedback for IoT NTN |
Huawei, HiSilicon |
| R1-2210947 |
Considerations for Disablement of HARQ in IoT NTN |
Lockheed Martin |
| R1-2211095 |
Disabling of HARQ for IoT NTN |
MediaTek Inc. |
| R1-2211111 |
Discussion on disabling of HARQ feedback for IoT-NTN |
ZTE |
| R1-2211178 |
Discussion on remaining issues of disabling of HARQ feedback for IoT NTN |
CATT |
| R1-2211248 |
Discussion on disabling of HARQ feedback for IoT NTN |
Spreadtrum Communications |
| R1-2211344 |
Discussion on the HARQ operation for IoT NTN |
xiaomi |
| R1-2211462 |
Discussion on disabling of HARQ feedback for IoT NTN |
OPPO |
| R1-2211548 |
Disabling of HARQ feedback for NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2211700 |
Discussion on disabling of HARQ feedback for IoT NTN |
CMCC |
| R1-2211734 |
Disabling of HARQ feedback in IoT-NTN |
InterDigital, Inc. |
| R1-2211756 |
On disabling HARQ feedback for IOT-NTN |
Mavenir |
| R1-2211767 |
On disabling HARQ feedback for IoT NTN |
Ericsson |
| R1-2211830 |
On HARQ Feedback Disabling for IoT NTN |
Apple |
| R1-2211884 |
Disabling of HARQ feedback for IoT NTN |
Lenovo |
| R1-2212066 |
Disabling of HARQ feedback for IoT NTN |
Samsung |
| R1-2212138 |
Disabling HARQ Feedback for IoT-NTN |
Qualcomm Incorporated |
| R1-2212242 |
Disabling of HARQ for IoT NTN |
MediaTek Inc. |
| R1-2212367 |
Disabling of HARQ feedback for IoT NTN |
NEC |
| R1-2212432 |
Disabling of HARQ feedback for IoT NTN |
Nordic Semiconductor ASA |
| R1-2212554 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2212555 |
FLS#2 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| 9.11.4 |
Improved GNSS operations for IoT NTN |
|
| R1-2210875 |
Discussion on improved GNSS operations for IoT NTN |
Huawei, HiSilicon |
| R1-2211096 |
Improved GNSS operations for IoT NTN |
MediaTek Inc. |
| R1-2211112 |
Discussion on improved GNSS operation for IoT-NTN |
ZTE |
| R1-2211179 |
Considerations on improved GNSS operationts for IoT NTN |
CATT |
| R1-2211249 |
Discussion on improved GNSS operations for IoT NTN |
Spreadtrum Communications |
| R1-2211345 |
Discussion on the improved GNSS operation for IoT NTN |
xiaomi |
| R1-2211463 |
Discussion on improved GNSS operations for IoT NTN |
OPPO |
| R1-2211549 |
Enhancements for long connections in NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2211701 |
Discussion on improved GNSS operations for IoT NTN |
CMCC |
| R1-2211735 |
GNSS acquisition and reporting in IoT NTN |
InterDigital, Inc. |
| R1-2211755 |
On Improved GNSS Operations for IoT NTN |
NEC |
| R1-2211764 |
On Improved GNSS operation in IoT NTN |
Ericsson Limited |
| R1-2211831 |
On Improved GNSS Operations for IoT NTN |
Apple |
| R1-2211885 |
Improved GNSS operations for IoT NTN |
Lenovo |
| R1-2212067 |
Improved GNSS operations for IoT NTN |
Samsung |
| R1-2212139 |
Improved GNSS Operations for IoT-NTN |
Qualcomm Incorporated |
| R1-2212243 |
Improved GNSS operations for IoT NT |
MediaTek Inc. |
| R1-2212433 |
Improved GNSS operation for IoT NTN |
Nordic Semiconductor ASA |
| R1-2212651 |
Feature lead summary#1 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2212652 |
Feature lead summary#2 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2212920 |
Feature lead summary#3 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| 9.12 |
Further NR mobility enhancements |
|
| R1-2212850 |
Session notes for 9.12 (Further NR mobility enhancements) |
Ad-Hoc Chair (CMCC) |
| 9.12.1 |
L1 enhancements for inter-cell beam management |
|
| R1-2210897 |
L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2210942 |
L1 enhancements for inter-cell beam management |
ZTE |
| R1-2211028 |
Discussion on L1 enhancements for L1/L2 mobility |
vivo |
| R1-2211053 |
L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2211083 |
Views on L1 enhancements for inter-cell beam management |
Fujitsu |
| R1-2211130 |
On Intercell beam management enhancement for NR mobility enhancement |
Google |
| R1-2211180 |
Discussion on L1 enhancements for inter-cell beam management |
CATT |
| R1-2211250 |
Discussion on L1 enhancements for inter-cell beam management |
Spreadtrum Communications |
| R1-2211297 |
L1 enhancements for inter-cell beam management |
Lenovo |
| R1-2211306 |
Discussion on L1 enhancements for L1/L2-triggered mobility |
Nokia, Nokia Shanghai Bell |
| R1-2211322 |
L1 enhancements for inter-cell beam management |
InterDigital, Inc. |
| R1-2211346 |
Discussion on L1 enhancements for inter-cell beam management |
xiaomi |
| R1-2211418 |
L1 Enhancements for Inter-cell Beam Management |
Intel Corporation |
| R1-2211440 |
Discussions on Inter-cell beam management enhancement |
OPPO |
| R1-2211702 |
Discussion on L1 enhancements for inter-cell beam management |
CMCC |
| R1-2211753 |
Discussion on L1 enhancements for inter-cell beam management |
NEC |
| R1-2211832 |
L1 enhancements to inter-cell beam management |
Apple |
| R1-2211873 |
Enhancements on inter-cell beam management for mobility |
LG Electronics |
| R1-2212004 |
Discussion on L1 enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2212068 |
On L1 enhancements for inter-cell beam management |
Samsung |
| R1-2212140 |
L1 Enhancements for Inter-Cell Beam Management |
Qualcomm Incorporated |
| R1-2212235 |
L1 enhancements for inter-cell beam management |
MediaTek Inc. |
| R1-2212741 |
FL summary 1 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2212858 |
FL summary 2 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2212946 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2212947 |
DRAFT LS on RAN1 agreements for L1/L2-based inter-cell mobility |
Fujitsu, CATT |
| R1-2212948 |
LS on RAN1 agreements for L1/L2-based inter-cell mobility |
RAN1, Fujitsu, CATT |
| 9.12.2 |
Timing advance management to reduce latency |
|
| R1-2210853 |
Comparison of TA acquisition schemes for L1/L2 Mobility |
FUTUREWEI |
| R1-2210898 |
Timing advance management to reduce latency |
Huawei, HiSilicon |
| R1-2210943 |
Enhancements on TA management to reduce latency |
ZTE |
| R1-2211029 |
Discussion on TA management for L1/L2 Mobility |
vivo |
| R1-2211131 |
On TA management for NR mobility enhancement |
Google |
| R1-2211181 |
Discussion on timing advance management to reduce latency |
CATT |
| R1-2211251 |
Discussion on timing advance management to reduce latency |
Spreadtrum Communications |
| R1-2211298 |
Timing advancement management for L1L2 mobility |
Lenovo |
| R1-2211307 |
Discussion on timing advance management for L1/L2-triggered mobility |
Nokia, Nokia Shanghai Bell |
| R1-2211323 |
Timing advance management to reduce latency |
InterDigital, Inc. |
| R1-2211347 |
Discussion on Timing advance management |
xiaomi |
| R1-2211419 |
On Timing Advance Management |
Intel Corporation |
| R1-2211441 |
Discussions on Timing Advance Management |
OPPO |
| R1-2211553 |
Timing advance management for L1/L2 Mobility |
Ericsson |
| R1-2211703 |
Discussion on timing advance management to reduce latency |
CMCC |
| R1-2211833 |
Timing advance management to reduce latency |
Apple |
| R1-2212005 |
Timing advance enhancement for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2212069 |
Candidate cell TA acquisition for NR L1/L2 mobility enhancement |
Samsung |
| R1-2212141 |
TA management to reduce latency for L1/L2 based mobility |
Qualcomm Incorporated |
| R1-2212239 |
UL Timing management to reduce handover latency |
MediaTek Inc. |
| R1-2212321 |
Reduced latency for inter-cell beam management |
Rakuten Symphony |
| R1-2212689 |
Moderator summary on Timing advance management: Round 1 |
Moderator (CATT) |
| R1-2212815 |
Moderator summary on Timing advance management: Round 2 |
Moderator (CATT) |
| R1-2212863 |
Moderator summary on Timing advance management: Round 3 |
Moderator (CATT) |
| 9.13.1 |
Evaluation on low power WUS |
|
| R1-2210850 |
Evaluation of Low Power WUS and Performance Results |
FUTUREWEI |
| R1-2210908 |
Evaluations for LP-WUS |
Huawei, HiSilicon |
| R1-2211030 |
Evaluation methodologies for R18 LP-WUS/WUR |
vivo |
| R1-2211182 |
Remaining issues of Deployment scenarios and evaluation methodologies for low-power wakeup receiver |
CATT |
| R1-2211252 |
Discussion on evaluation on low power WUS |
Spreadtrum Communications |
| R1-2211269 |
Low power WUS Evaluation Methodology |
Nokia, Nokia Shanghai Bell |
| R1-2211319 |
Discussion on evaluation on LP-WUS |
InterDigital, Inc. |
| R1-2211325 |
Power requirement for WUS |
Everactive |
| R1-2211348 |
Evaluation on low power WUS |
xiaomi |
| R1-2211420 |
Discussion on evaluations on LP WUS |
Intel Corporation |
| R1-2211471 |
Evaluation for lower power wake-up signal |
OPPO |
| R1-2211628 |
Evaluation of low power WUS |
Sony |
| R1-2211834 |
On performance evaluation for low power wake-up signal |
Apple |
| R1-2211907 |
Evaluation on LP-WUS |
ZTE, Sanechips |
| R1-2212006 |
Discussion on evaluation methodology for low power WUS |
NTT DOCOMO, INC. |
| R1-2212070 |
Evaluation on LP-WUS/WUR |
Samsung |
| R1-2212142 |
Evaluation methodology for LP-WUS |
Qualcomm Incorporated |
| R1-2212158 |
Evaluation framework for low power WUS |
Ericsson |
| R1-2212261 |
Evaluation on low power WUS |
MediaTek Inc. |
| R1-2212316 |
Evaluation of low power WUS |
Rakuten Symphony |
| R1-2212384 |
Discussion on Evaluation on Low power WUS |
EURECOM |
| R1-2212410 |
Discussion on the evaluation for low power WUS |
Lenovo |
| R1-2212417 |
On LP-WUS evaluation |
Nordic Semiconductor ASA |
| R1-2212693 |
void |
MCC ETSI |
| R1-2212768 |
FL summary#1 of evaluation on low power WUS |
Moderator (vivo) |
| R1-2212899 |
FL summary#2 of evaluation on low power WUS |
Moderator (vivo) |
| R1-2213005 |
Final FL summary of evaluation on low power WUS |
Moderator (vivo) |
| 9.13.2 |
Low power WUS receiver architectures |
|
| R1-2210909 |
Discussion on architecture of LP-WUS receiver |
Huawei, HiSilicon |
| R1-2211031 |
Discussion on low power wake-up receiver architecture |
vivo |
| R1-2211067 |
Low Power WUS receiver architecture |
TCL Communication Ltd. |
| R1-2211183 |
Low-Power WUS receiver Architectures and its performance |
CATT |
| R1-2211253 |
Discussion on low power WUS receiver architectures |
Spreadtrum Communications, H3C |
| R1-2211270 |
Low Power WUS Receiver Architectures |
Nokia, Nokia Shanghai Bell |
| R1-2211320 |
Discussion on LP-WUS receiver architectures |
InterDigital, Inc. |
| R1-2211326 |
FSK Architectures for WUR |
Everactive |
| R1-2211421 |
Discussion on LP-WUS receiver architecture |
Intel Corporation |
| R1-2211472 |
Discussion on low power WUS receiver |
OPPO |
| R1-2211599 |
Discussion on low power wake up receiver architectures |
Panasonic |
| R1-2211835 |
On low power wake-up receiver architectures |
Apple |
| R1-2211908 |
LP-WUS receiver architectures |
ZTE, Sanechips |
| R1-2212007 |
Discussion on low power WUS receiver architectures |
NTT DOCOMO, INC. |
| R1-2212071 |
Receiver architecture for LP-WUS |
Samsung |
| R1-2212143 |
Receiver architecture for LP-WUS |
Qualcomm Incorporated |
| R1-2212159 |
Low power WUS receiver architectures |
Ericsson |
| R1-2212262 |
Low power WUS receiver architectures |
MediaTek Inc. |
| R1-2212317 |
Receiver architectures for low power WUS |
Rakuten Symphony |
| R1-2212411 |
Design consideration of Low-Power WUS receiver |
Lenovo |
| R1-2212418 |
On LP-WUS architecture |
Nordic Semiconductor ASA |
| R1-2212674 |
Summary #1 on LP WUR architecture |
Moderator (Apple) |
| R1-2212675 |
Summary #2 on LP WUR architecture |
Moderator (Apple) |
| R1-2212676 |
Summary #3 on LP WUR architecture |
Moderator (Apple) |
| R1-2212953 |
Draft LS to RAN4 on low-power wake-up receiver architectures |
Moderator (Apple) |
| R1-2212999 |
LS to RAN4 on low-power wake-up receiver architectures |
RAN1, Apple, vivo |
| 9.13.3 |
L1 signal design and procedure for low power WUS |
|
| R1-2210851 |
Low Power WUS Design |
FUTUREWEI |
| R1-2210910 |
Signal design and procedure for LP-WUS |
Huawei, HiSilicon |
| R1-2211032 |
Discussion on physical signal and procedure for low power WUS |
vivo |
| R1-2211068 |
L1 signal design and procedure for low power WUS |
TCL Communication Ltd. |
| R1-2211184 |
Physical layer signals and procedures for Low-Power WUS |
CATT |
| R1-2211271 |
L1 signal design and procedures for low power WUS |
Nokia, Nokia Shanghai Bell |
| R1-2211321 |
Discussion on L1 signal design and procedure for LP-WUS |
InterDigital, Inc. |
| R1-2211327 |
L1 WUS Considerations |
Everactive |
| R1-2211349 |
Discussions on L1 signal design and procedure for low power WUS |
xiaomi |
| R1-2211422 |
Discussions on L1 signal design and procedure for low power WUS |
Intel Corporation |
| R1-2211473 |
L1 signal design consideration on lower power wake-up signal |
OPPO |
| R1-2211546 |
Discussion on L1 signal design and procedure for low power WUS |
Spreadtrum Communications |
| R1-2211600 |
Discussion on low power wake up signal design |
Panasonic |
| R1-2211629 |
L1 signal design and procedure for LP-WUS |
Sony |
| R1-2211704 |
Discussion on L1 signal design and procedure for LP-WUS |
CMCC |
| R1-2211836 |
On the L1 signal design and procedures for low power wake-up signal |
Apple |
| R1-2211857 |
L1 signal design and procedure for low power WUS |
Sharp |
| R1-2211909 |
LP-WUS design and related procedure |
ZTE, Sanechips |
| R1-2212008 |
Discussion on L1 signal design and procedure for low power WUS |
NTT DOCOMO, INC. |
| R1-2212072 |
Signal design and procedure for LP-WUS |
Samsung |
| R1-2212144 |
L1 signal design and procedures for LP-WUR |
Qualcomm Incorporated |
| R1-2212160 |
L1 signal design and procedure for low power WUS |
Ericsson |
| R1-2212263 |
L1 signal design and procedure for low power WUS |
MediaTek Inc. |
| R1-2212318 |
L1 signal design for low power WUS |
Rakuten Symphony |
| R1-2212366 |
Discussion on L1 signal design and procedure for LP-WUS |
NEC |
| R1-2212385 |
Discussion on L1 signal design and procedure for low power WUS |
EURECOM |
| R1-2212412 |
Discussion on the L1 signal design and procedure for low power WUS |
Lenovo |
| R1-2212419 |
On LP-WUS signal design |
Nordic Semiconductor ASA |
| R1-2212749 |
Summary #1 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2212866 |
Summary #2 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2212978 |
Final summary of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| 9.14 |
Further NR coverage enhancements |
|
| R1-2212851 |
Session notes for 9.14 (Further NR coverage enhancements) |
Ad-Hoc Chair (CMCC) |
| 9.14.1 |
PRACH coverage enhancements |
|
| R1-2210879 |
Discussion on PRACH coverage enhancements |
Huawei, HiSilicon |
| R1-2211033 |
Discussions on issues of PRACH coverage enhancements |
vivo |
| R1-2211047 |
Discussion on PRACH coverage enhancements |
ZTE |
| R1-2211087 |
Discussion on PRACH coverage enhancements |
Fujitsu |
| R1-2211185 |
PRACH coverage enhancements |
CATT |
| R1-2211254 |
Discussion on PRACH coverage enhancements |
Spreadtrum Communications |
| R1-2211350 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2211423 |
Discussions on PRACH coverage enhancement |
Intel Corporation |
| R1-2211474 |
PRACH coverage enhancements |
OPPO |
| R1-2211537 |
Discussion on PRACH coverage enhancement |
China Telecom |
| R1-2211541 |
PRACH coverage enhancements |
TCL Communication Ltd. |
| R1-2211568 |
PRACH coverage enhancements |
ETRI |
| R1-2211573 |
PRACH coverage enhancements |
Lenovo |
| R1-2211592 |
Discussion on PRACH coverage enhancements |
Panasonic |
| R1-2211595 |
PRACH coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2211630 |
PRACH Coverage Enhancement using Multi PRACH Transmissions |
Sony |
| R1-2211705 |
Discussion on PRACH coverage enhancements |
CMCC |
| R1-2211711 |
Discussion on PRACH coverage enhancements |
InterDigital, Inc. |
| R1-2211837 |
Discussion on PRACH coverage enhancement |
Apple |
| R1-2211881 |
Discussion on PRACH Resource for multiple PRACH transmissions |
FGI |
| R1-2211895 |
Discussion on PRACH coverage enhancement |
Ericsson |
| R1-2211931 |
Discussion on PRACH repeated transmission for NR coverage enhancement |
LG Electronics |
| R1-2212009 |
Discussion on PRACH coverage enhancements |
NTT DOCOMO, INC. |
| R1-2212073 |
PRACH coverage enhancements |
Samsung |
| R1-2212145 |
PRACH Coverage Enhancements |
Qualcomm Incorporated |
| R1-2212181 |
Views on multiple PRACH transmission for coverage enhancement |
Sharp |
| R1-2212255 |
Discussion on PRACH coverage enhancements |
MediaTek Inc. |
| R1-2212273 |
Discussion on issues of PRACH coverage enhancement |
Mavenir |
| R1-2212360 |
Discussion on PRACH coverage enhancement |
NEC |
| R1-2212562 |
Discussion on PRACH coverage enhancement |
Ericsson |
| R1-2212566 |
FL Summary#1 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2212567 |
FL Summary#2 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2212568 |
FL Summary#3 on PRACH coverage enhancements |
Moderator (China Telecom) |
| 9.14.2 |
Power domain enhancements |
|
| R1-2210880 |
Discussion on coverage enhancement in power domain |
Huawei, HiSilicon |
| R1-2211034 |
Discussions on issues of power domain enhancements |
vivo |
| R1-2211048 |
Discussion on power domain enhancements |
ZTE |
| R1-2211088 |
Discussion on Power domain enhancements for CA/DC |
Fujitsu |
| R1-2211186 |
Discussion on enhancements to reduce MPR/PAR |
CATT |
| R1-2211255 |
Discussion on power domain enhancements |
Spreadtrum Communications |
| R1-2211351 |
Discussion on power domain enhancements |
xiaomi |
| R1-2211424 |
Discussions on power domain enhancement |
Intel Corporation |
| R1-2211475 |
The study of power domain enhancements |
OPPO |
| R1-2211574 |
Power domain enhancements |
Lenovo |
| R1-2211593 |
Discussion on power domain enhancements |
Panasonic |
| R1-2211596 |
RAN1 impacts for power domain enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2211706 |
Discussion on power domain enhancements |
CMCC |
| R1-2211712 |
Discussion on power domain enhancements |
InterDigital, Inc. |
| R1-2211838 |
Discussion on power domain coverage enhancement |
Apple |
| R1-2211896 |
Power Domain Enhancement Evaluation Methodology and Schemes |
Ericsson |
| R1-2212010 |
Discussion on power domain enhancements |
NTT DOCOMO, INC. |
| R1-2212074 |
Power domain enhancements |
Samsung |
| R1-2212146 |
Power-domain enhancements |
Qualcomm Incorporated |
| R1-2212182 |
Power domain enhancements for Rel-18 CovEnh |
Sharp |
| R1-2212256 |
Discussion on power domain enhancements |
MediaTek Inc. |
| R1-2212282 |
DMRS design for power domain enhancements |
Indian Institute of Tech (H) |
| R1-2212573 |
FL summary of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2212574 |
FL summary #2 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2212575 |
FL summary #3 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2212576 |
FL summary #4 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2212577 |
Final FL summary of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2212916 |
[Draft] LS to RAN4 for further information on RAN1 assumptions for LLS performance evaluation of MPR/PAR reduction solutions |
Moderator (Nokia) |
| R1-2212917 |
LS to RAN4 for further information on RAN1 assumptions for LLS performance evaluation of MPR/PAR reduction solutions |
RAN1, Nokia |
| R1-2212918 |
Template for reporting results of LLS performance evaluations of MPR/PAR reduction solutions |
Moderator (Nokia) |
| 9.14.3 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
|
| R1-2210881 |
Discussion on dynamic waveform switching for coverage enhancement |
Huawei, HiSilicon |
| R1-2211035 |
Discussions on issues of dynamic waveform switching |
vivo |
| R1-2211049 |
Discussion on dynamic waveform switching |
ZTE |
| R1-2211089 |
Discussion on Dynamic switching between DFT-s-OFDM and CP-OFDM |
Fujitsu |
| R1-2211134 |
Discussion on dynamic waveform switching |
Panasonic |
| R1-2211187 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
CATT |
| R1-2211256 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Spreadtrum Communications |
| R1-2211324 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2211352 |
Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM |
xiaomi |
| R1-2211390 |
Dynamic switching between DFT-S-OFDM and CP-OFDM waveform |
Intel Corporation |
| R1-2211476 |
Considerations on dynamic switching between DFT-S-OFDM and CP-OFDM |
OPPO |
| R1-2211538 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
China Telecom |
| R1-2211569 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
ETRI |
| R1-2211575 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Lenovo |
| R1-2211597 |
Dynamic switching between DFT-s-OFDM and CP-OFDM |
Nokia, Nokia Shanghai Bell |
| R1-2211631 |
Further considerations on dynamic waveform switching for NR UL |
Sony |
| R1-2211707 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
CMCC |
| R1-2211839 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Apple |
| R1-2211879 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
FGI |
| R1-2211897 |
Discussion on Dynamic UL Waveform Switching |
Ericsson |
| R1-2211932 |
Discussion on dynamic waveform switching for NR coverage enhancement |
LG Electronics |
| R1-2212011 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NTT DOCOMO, INC. |
| R1-2212075 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Samsung |
| R1-2212147 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Qualcomm Incorporated |
| R1-2212183 |
Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh |
Sharp |
| R1-2212257 |
Dynamic switching between waveforms |
MediaTek Inc. |
| R1-2212272 |
Discussion on Dynamic switching mechanism of CP-OFDM and DFT-S-OFDM |
Mavenir |
| R1-2212361 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NEC |
| R1-2212431 |
Discussion on Dynamic switching between DFT-S-OFDM and CP-OFDM |
CEWiT |
| R1-2212445 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2212446 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2212983 |
Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| 9.16 |
NR support for dedicated spectrum less than 5MHz for FR1 |
|
| R1-2212398 |
Work Plan for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R1-2212852 |
Session notes for 9.16 (NR support for dedicated spectrum less than 5MHz for FR1) |
Ad-hoc Chair (CMCC) |
| 9.16.1 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
|
| R1-2210834 |
Enhancements for less than 5 MHz dedicated spectrum |
FUTUREWEI |
| R1-2210869 |
Discussion on dedicated spectrum less than 5 MHz for FR1 |
Huawei, HiSilicon |
| R1-2211036 |
Discussion on NR support for dedicated spectrum less than 5MHz |
vivo |
| R1-2211050 |
Discussion on dedicated spectrum less than 5MHz for FR1 |
ZTE |
| R1-2211132 |
PBCH design for dedicated spectrum less than 5MHz for FR1 |
TD Tech, Chengdu TD Tech |
| R1-2211353 |
Views on enhancements to operate NR on dedicated spectrum less than 5 MHz |
xiaomi |
| R1-2211391 |
Discussion on NR operation with less than 5MHz Bandwidth |
Intel Corporation |
| R1-2211547 |
Discussion on enhancements to operate NR on dedicated spectrum |
Spreadtrum Communications |
| R1-2211572 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
Lenovo |
| R1-2211770 |
NR support of spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2212012 |
Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz |
NTT DOCOMO, INC. |
| R1-2212076 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
Samsung |
| R1-2212148 |
NR support for dedicated spectrum less than 5MHz in FR1 |
Qualcomm Incorporated |
| R1-2212247 |
On dedicated spectrum less than 5 MHz |
MediaTek Inc. |
| R1-2212307 |
Discussion on enhancements for dedicated spectrum less than 5 MHz |
LG Electronics |
| R1-2212397 |
NR support for below 5 MHz BW |
Nokia, Nokia Shanghai Bell |
| R1-2212755 |
Summary of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2212888 |
Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2212898 |
[Draft] LS on NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia |
| R1-2212919 |
LS on NR support for dedicated spectrum less than 5MHz for FR1 |
RAN1, Nokia |
| 9.17 |
Other |
|
| R1-2211037 |
Remaining issues on Rel-18 NR Dynamic spectrum sharing |
vivo |
| R1-2211286 |
[eDSS] RRC configuration and UE capability for PDCCH on CRS |
Nokia, Nokia Shanghai Bell |
| R1-2211487 |
Discussion on remaining issues in Rel-18 eDSS |
OPPO |
| R1-2211652 |
Discussion on remaining issues for Rel-18 DSS |
ZTE |
| R1-2212013 |
Remaining issues on NR PDCCH reception in symbols with LTE CRS REs |
NTT DOCOMO, INC. |
| R1-2212454 |
Remaining issues on NR PDCCH reception in symbols with LTE CRS REs |
Huawei, HiSilicon |